Terminal-to-terminal communication connection control system for IP full service

ABSTRACT

The present invention relates to a terminal-to-terminal communication connection control method using an IP network characterized in that: in order for a mobile telephone set to have a telephone communication with a fixed telephone set by way of a mobile communication network and an IP network, the mobile communication network carries out a line connection control based on the common channel signaling system; the IP network establishing a communication path by carrying out a line connection control applying a common channel signaling system to the IP network thereby effecting a telephone communication.

BACKGROUND OF THE INVENTION

[0001] 1. Field of the Invention

[0002] The present invention relates to a terminal-to-terminalcommunication connection control system for IP (Internet Protocol)service including IP-service terminal-to-terminal communicationconnection control system of any or a combination of aterminal-to-terminal communication connection control method forcooperating an IP network (called also an IP transfer network) withanother communication network, a terminal-to-terminal connection controlmethod for an IP network applied with the No. 7 common channel signalingsystem, a terminal-to-terminal connection control method based on anIP-network multicast technique, an apparatus for realizingterminal-to-terminal communication connection control and multicastservice or TV conference service. The other communication networkincludes a public switched telephone network (PSTN) and a mobilecommunication network used for mobile phones, besides the IP network.

[0003] 2. Description of the Related Art

[0004] The prior arts related to the present invention includes JapanesePatent No. 3084681 C1 (hereinafter, “prior patent”) by the presentapplicants and Japanese Patent Application No. 078270/2001 (hereinafter,“prior patent application”) by the present applicants.

[0005] The prior patent realizes, in an integrated informationcommunication system as an IP packet transfer network adopting an IPencapsulation technique, an IP encapsulation technique, a technique ofdynamically setting an address management table by IP-terminal request,and a method of acquiring an IP address by presenting a telephone numberto a domain server to register the acquired address in a addressmanagement table. Meanwhile, the prior patent application discloses, ina terminal-to-terminal communication connection method using an IPpacket transfer network, a simplified encapsulation technique, a methodof applying the common channel signaling system onto an IP network, amethod of carrying out multicast by registering a user's terminal-unitaddress into the network node unit, and so on.

[0006] Note that the prior patent or patent application uses the termsnot the same as the terms used in the present invention. Accordingly,the terms used in the prior patent or patent application will be shownwith parentheses in order to avoid confusion. For example, in the caseof describing a network node unit (access control apparatus), the accesscontrol apparatus is a term used in the prior patent or patentapplication.

[0007] <<IP Encapsulation Technique>>

[0008] The IP encapsulation technique disclosed in the prior patent willbe outlined with reference to FIG. 1. In this example, an external IPpacket 13-1 is transferred from an IP terminal unit 12-1 having anexternal IP address “EA01” to an IP terminal unit 12-2 having anexternal IP address “EA02” via an IP network 11-1. A logic communicationline 12-3 has an end (logic terminal) to be identified by a logicterminal identifier “Pin1” while a logic communication line 12-4 has anend to be identified by a logic terminal identifier “Pin2”. The logicterminal “Pin1” is given with an internal IP address “IA01”, and thelogic terminal “Pin2” is given with an internal IP address “IA02”. Thenetwork node unit 11-2, receiving an external IP packet 13-1, confirmsthat an internal IP address given to the logic terminal “Pin1” inputtedby the IP packet 13-1 is “IA01” and a destination IP address of the IPpacket 13-1 is “EA02”, to search through the interior of an addressmanagement table 11-8. Searched are records including, first, a sourceinternal IP address of “IA01” and, next, a destination external IPaddress of “EA02”. Furthermore, inspection is made whether the detectedrecord includes a source external IP address “EA01” of within the IPpacket 13-1. In the present example, this is a record including “Pin1,IA01, IA02, EA01, EA02” on a second line from above. Using the IPaddresses “IA01” and “IA02” of the record, an IP packet 13-2 is formed(IP packet encapsulation).

[0009] The internal IP packet 13-2 passes through routers 11-4, 11-5,11-6 to reach a network node unit 11-3. The network node unit 11-2removes the received internal IP packet 13-2 of an IP header (IP packetdecapsulation) and forwards an obtained external IP packet 13-3 onto acommunication line 12-4. An IP terminal unit 12-3 receives the externalIP packet 13-3. The fist-lined record “Pin1, IA01, IA81, EA01, EA81” ofan address management table 11-8 is used to encapsulate an external IPpacket directed toward a server 11-7 having an external IP address“EA81” and an internal IP address “IA81”. By changing a destinationexternal IP address of an external IP packet inputted at the same logicterminal (terminal end of a logic communication line 12-3) to “EA01”,“EA81” or so, the destination where the external IP packet is to reachcan be changed. Note that the mask technique in IP encapsulation isknown, e.g. explained in FIG. 362 of the prior patent application.

[0010] <<Simplified Encapsulation Technique>>

[0011] With reference to FIG. 2, outlined is a simplified encapsulationtechnique disclosed in the prior patent application. The internal packetformed by simplified encapsulation is different from the foregoing IPencapsulation in that containing a destination internal address but notcontaining a source internal address. A logic communication line 22-3 atits end (logic terminal) is determined by a logic terminal identifier“Pin1” while a logic communication line 22-4 at its end (logic terminal)is determined by a logic terminal identifier “Pin2”. An internal IPaddress “IA01” is provided to the logic terminal “Pin1”, and an internalIP address “IA02” is provided to the logic terminal “Pin2”. In thepresent example, an external IP packet 23-1 is transferred from an IPterminal unit 22-1 having an external IP address “EA01” to an IPterminal unit 22-2 having an external IP address “EA02”. The networknode unit 21-2, upon receiving an external IP packet 23-1, confirms thatan internal IP address given to the logic terminal “Pin1” inputted bythe IP packet 23-1 is “IA01” and a destination external IP address ofthe IP packet 23-1 is “EA02”, to search an address management table21-8. Searched are records including, first, a source internal IPaddress of “IA01” and, next, a destination external IP address of“EA02”. Furthermore, inspection is made whether the detected recordincludes a source external IP address “EA01” of within the IP packet23-1. In the present example, fallen under is a record including “Pin1,IA01, IA02, EA01, EA02” on a second line from above. The IP addresses“IA01” and “IA02” in the record are used to form an IP packet 13-2having a simplified header whose destination IP address is “IA02”(simplified encapsulation). The internal IP packet 23-2 reaches anetwork node unit 21-3 by way of routers 21-4, 21-5, 21-6. The networknode unit 21-2 removes the received internal IP packet 23-2 of itssimplified header (simplified decapsulation) and forwards an obtainedexternal IP packet 23-3 onto a communication line 22-4. The internalpacket is to be realized by an optical frame having communication twolayers including, for example, only a destination address. Such anoptical frame includes a MAPOS being known, for example.

[0012] Incidentally, the IP encapsulation and the simplified IPencapsulation, in any, can use as a logic terminal identifier a logicalterminal identification number at an end of a communication two-layeredaddress (physical address, MAC address or the like), for example.Meanwhile, similarly to the IP encapsulation technique, a destinationwhere an external packet is to reach can be changed by changing adestination external IP address of within the external IP packetinputted at the same logic terminal.

[0013] <<Technique for Dynamically Setting Address Management Table uponRequest of IP Terminal Unit>>

[0014] The prior patent discloses, in Embodiment 35, a method to changea setting content of an address management table (conversion table) ofwithin a network node unit (access control apparatus) from a user's IPterminal. This will be explained with reference to FIG. 3.

[0015] An IP terminal unit 23-1 sends an external IP packet (ICS userframe) containing a domain name “c5. b2. a1” to a conversion tableserver 23-2 (Step 23-4). The conversion table server 23-2 makes aninquiry to the domain name server 23-3 (Step 23-5). The domain nameserver 23-3 searches for and acquires an internal address (ICS networkaddress) and external IP address (ICS user address) corresponding to thedomain name “c5. b2. a1” (Step 23-6). Then, this is sent back to theconversion table server 23-2 (Step 23-7). The conversion table server23-2 writes it into a conversion table (Step 23-8), for report to the IPterminal 23-1 (Step 23-9).

[0016] <<Method for Acquiring IP Address by Telephone Number as DomainName>>

[0017] Next, Embodiment 36 of the prior patent discloses that IP packets(ICS user frames) can be communicated with the other end ofcommunication by using a telephone number as a domain name wherein theIP packet stores therein a digitalized voice thereby enabling publiccommunication by the telephone. An address management server (conversiontable server) converts an input domain name into an external IP address(ICS user address) to send it back, and registers an internal address(ICS network address) in an address management table (conversion table)of the network node unit (access control apparatus).

[0018] A telephone number “1234-5678” inputted to a telephone set isdelivered to a conversion table server via a telephone number inputsection of the telephone set. The conversion table server 24-4 (FIG. 4)makes an inquiry to a plurality of domain name servers 24-1, 24-2, 24-3one after another (24-6 to 24-11 in FIG. 4) on the basis of the receivedtelephone number “1234-5678”, and acquires an internal address andexternal IP address of a telephone set at the other end of communicationupon considering the telephone number “1234-5678” as a domain name.Next, the conversion table server 24-4 prepares a new item to be addedto the address management table (conversion table) of within the networknode unit by using acquired two addresses, and sends it to a requestingtelephone set. Also, the network node unit uses the new item of theaddress management table as a new element of the address managementtable in the network node unit.

[0019] <<Method for Applying the No. 7 Common Channel Signaling Systemto IP Network>>

[0020] This is a technique disclosed in the prior patent application. Asshown in FIG. 5, connection servers 25-5 to 25-6 and a relay connectionserver 25-7 are provided in an IP network 25, to connect terminal units25-1 and 25-2 to the connection server via a media router 25-3 or 25-4.Note that the connection server and the relay connection server arereferred also to as telephone management servers. The connection servers25-5 and 25-6 are provided with a function similar to theline-connection control of a line switch (LS) in a public switchedtelephone network (PSTN) while the relay connection server 25-7 is witha function similar to the line-connection control of a tall switch (TS).Terminal units, such as telephone sets, IP terminal units or videoterminal units, send and receive an initial address message (IAM)capable of making equally corresponding to the line-connection controlmessage of the common channel signing system, an address completemessage (ACM), a call progress message (CPG), an answer message (ANM), arelease message (REL) and a release completion message (RLC) by way ofan interior of the IP network, thereby realizing a terminal-to-terminalcommunication connection control method using an IP network. Note that aterminal-to-terminal communication connection control method is feasiblebetween the two connection servers 25-5 and 25-6 wherein a relayconnection server 25-7 does not exist.

[0021] The utilizer inputs a destination telephone number on theterminal unit 25-1 (Step Z1). The media router 25-3 sends back a callset acceptance (Step Z2). The media router 25-3 sends an IP packetincluding a destination telephone number and source telephone number toset a call (Step Y1). An IAM packet forwarded from the connection server25-5 passes the connection server 25-6 (Steps Y2, Y3) to reach the mediarouter 25-4 (Step Y4). The media router 25-4 requests the terminal unit25-2 to set a call (Step Z4). The connection server 25-6 sends back anACM packet (Steps Y5, Y6). The terminal unit 25-2 reports of an incomingcall tone (Step Z7). The media router 25-4 sends an incoming call to theconnection server 25-6 (Step Y7). The connection server 25-6 sends a CPGpacket (Steps Y8, Y9) to notify a ring-back tone to the terminal unit25-1 via the media router 25-3 (Step Y10, Step Z10). The terminal unit25-2, responding to the call set request, makes a notification to theconnection server 25-6 (Step Z11, Step Y11). The connection server 25-6forms and sends an ANM packet. The terminal unit 25-1 enters into avoice communication phase (Steps Y12 to Y14, Step Z14).

[0022] When the utilizer ends the voice communication on the terminalunit 25-1, a disconnect request on the terminal unit 25-1 is notified(Step Z16). A REL packet signifying a series of release requests and aRLC packet meaning a completion of release request are communicated,thereby closing the call connection (Steps Y16 to Y23, Steps Z22 andZ23). The step of between the connection server 25-2 and the connectionserver 25-6 (Y2, Y3, etc.) is referred to as an NNI, while the step ofbetween the connection server and the media router (Y1, Y3, etc.) isreferred to as a UNI.

[0023] <<Detailed Example of Between IP Network Applied with CommonChannel Signaling System and Public Switched Telephone Network>>

[0024] The Embodiments 13 to 16 of the prior patent application,adopting a concept of the common channel signaling system, have afeature of separating the interior of an IP network with a controlcommunication line and a voice communication line. This discloses amethod of controlling the communication connection between telephonesets through the IP network and public switched telephone network. InFIG. 6, numeral 40-1 is an IP network, numeral 40-2 is a public switchedtelephone network, numeral 40-3 is a gateway having an encapsulationfunction, numeral 40-4 is a relay gateway, numeral 40-5 is an IPcommunication line, numeral 40-6 is a control communication line on thecommon channel signaling system, and numeral 40-7 is a voicecommunication line. Numeral 40-8 is a control IP communication line andnumeral 40-9 is a voice IP communication line. Numerals 41-1 and 41-2are telephone sets, numeral 41-3 is a media router, numeral 42-1 is atall switch, numeral 42-2 is a subscriber exchange, numeral 42-3 is arelay control section (STP), numeral 42-4 is a voice control sectionhaving an encapsulation function, and numeral 42-5 is a terminal-unitcontrol section (SEP). Numeral 43-1 is a proxy telephone server, numeral43-2 is a telephone management server, numeral 43-3 is a telephonenumber server, numerals 43-4 and 43-5 are table management servers,numerals 44-1 and 44-2 are network node units having encapsulation anddecapsulation functions, numerals 44-3, 44-4, 44-5, 44-6 arerespectively routers. The relay control section 42-3 is given with an IPaddress. The relay control section 42-3 is a signal transfer point (STP)on the common channel signaling system. as viewed from the publicswitched telephone network 40-2, and given with a signaling pointaddress.

[0025] The terminal-unit control section 42-5 of FIG. 6 corresponds tothe connection server 25-5 of FIG. 5, and the relay control section 42-3of FIG. 6 corresponds to the relay connection server 25-7 of FIG. 5.Herein, “correspondence” means that the terminal unit control section42-5 and the relay control section 42-3 have a function to effectline-connection control based on the common channel signaling system.

[0026] In case the telephone set 41-1 requests a call set to thetelephone set 41-2, an initial address message (IAM), an addresscompletion message (ACM), a call progress message (CPG), an answermessage (ANM), a release message (REL), a release completion message(RLC) and the like are communicated by way of the media router 41-3,network node unit 44-1, terminal-unit control section 42-5, routers 44-4to 44-5, relay control section 42-3, control communication line 40-6,exchange 42-1 and exchange 42-2, thereby effecting aterminal-to-terminal communication connection control using the IPnetwork. Herein, the voice forwarded from the telephone set 41-1 reachesthe telephone set 41-2 by way of the media router 41-3, network nodeunit 44-1, router 44-6, network node unit 44-2, voice IP communicationline having a function of voice control section encapsulation 40-9,exchange 42-1 and exchange 42-2.

[0027] The relay control section 42-3 defines the various parameters tobe defined by the common signaling system, e.g. circuit identificationcode (CIC) and signaling link selection (SLS), according to a rulepreviously arranged with the public switched telephone network 40-2. Therelay control section 42-3 writes a signaling point address, signalinglink selection and circuit identification code of the relay controlsection 42-3, together with a media path identifier, to an addressconnection table 45-1. The relay control section 42-3, managing agateway address management table 45-2, can search through the gatewayaddress management table 45-2 to acquire an IP address of a gatewaymanaging a destination telephone number, i.e. an IP of a gateway forconnection to a telephone set having a destination telephone number. Therelay control section 42-3, managing a signaling point addressmanagement table 45-3, can search through the signaling point addressmanagement table to acquire a signaling point address of an exchange ofwithin the public switched telephone network 40-2. The relay controlsection 42-3 makes a notification to the encapsulation-functioned voicecontrol section 42-4 via an information line 45-4. Theencapsulation-functioned voice control section 42-4 writes the notifiedinformation as a record of the media path connection table 45-4 andmakes notification of a write completion. The media path identifier isused to identify a voice communication path used for a telephone call(connection/voice communication/release) of between telephone sets.Incidentally, the encapsulation-functioned voice control section 42-4 isconfigured to define a logic communication line for transmit a voicefrom the encapsulation-functioned voice control section 42-4 onto thevoice communication line 40-7 and write the logic communication lineidentifier as a record of the media path connection table 45-4.

[0028] The encapsulation-functioned voice control section 42-4 convertsa voice stored in an IP packet forwarded from the voice IP communicationline 40-9 into a form for transfer within the public switched telephonenetwork 40-2, and sends it onto the voice communication line 40-7. Also,the encapsulation-functioned voice control section 42-4 converts a voiceframe forwarded from the voice communication line 40-7 of the publicswitched telephone network 40-2 into an IP packet form, and sends itonto the voice IP communication line 40-9. The voice control section hastherein an IP address to send and receive a voice IP packet, thusserving for a setting of the media path connection table 45-4.

[0029] The prior patent application discloses a technique fortransferring a message (IAM, ACM, . . . , REL, etc.) for telephoneline-connection control by storing it in an IP packet (FIG. 142, etc. oftenth embodiment). The line control conforming to the common linesignaling system is applied to a level above the three layers of acommunication layer (network layer).

[0030] The line-connection control messages (IAM, ACM, CPG, ANM, REL,RLC) conforming to the common channel signaling system are to be set ina payload section of an internal IP packet. Explanation will be madeusing a protocol stack 59-1, 59-2 (FIG. 7). In designating a protocoltype as an item in a header of an internal IP packet, there is a methodof defining “CC” (connection control) representative of line-connectioncontrol as a new prototype to store the line-connection control messagesin a payload section of the internal IP packet. As another method, thereis a method of designating the protocol type as “ICMP” to store theline-connection control messages in an ICMP message area in the internalIP packet.

[0031] As a still another method, there is a method of designating theprotocol type as “UDP” to store the line-connection control messages ina payload section in a UDP segment of an internal IP packet. The methodwith a protocol stack 59-1 is a method of providing a data link layer ona physical layer as the lowermost layer, an IP layer thereon (networklayer), and a new line-connection control layer (CC layer) in a levelthat. The method with a protocol stack 59-2 is a method of providing aUDP layer or ICMP layer in a level above an IP layer, and aline-connection control layer (CC layer) thereon.

[0032] The fourteenth embodiment of the prior patent applicationexplains, as shown in FIG. 8 (part of FIG. 232 of the prior patentapplication), a terminal-to-terminal communication connection controlmethod to carry out a telephone communication from a telephone set 1420to a telephone set 1421 by way of a public switched telephone network1405, an IP network 1400 and a public switched telephone network 1406.Outlining will be made on a scope concerned with the invention.

[0033] When taking a receiver of the telephone set 1420, a signal unit1451 based on the common channel signaling system is transferred to therelay control section 1423 of within a relay gateway 1401 via a controlcommunication line 1415. The signal unit 1451 has a destination pointcode of “DPC-1”, a source point code of “OPC-1”, a signaling linkselection of “SLS-1”, a circuit identification code of “CIC-1”, amessage of “IAM” and a parameter of “Para-1”. The parameter “Para-1” hasa content including a telephone number “TN-1” of the telephone set 1420and a telephone number “TN-2” of the telephone set 1421. The relaycontrol section 1423 receives the signal unit 1451 and forms an IPpacket 1451. The IP packet 1452 has a destination IP address of“D-ad-x”, a source IP address of “S-ad-x” and a circuit identificationcode of “CIC-x”, and includes a telephone number “TN-1” of the telephoneset 1420 and a telephone number “TN-2” of the telephone set 1421. Therelay control section 1423 sends the IP packet 1452 formed in the aboveinto the IP network 1400. The IP packet 1452 reaches the relay controlsection 1424 of within the relay gateway 1402, which, in the relaycontrol section 1424, is converted into a signal unit 1453 to reach thetelephone set 1421 via the public switched telephone network 1406. Therelay control section 1423 and the voice control section 1427 exchangeinformation, such as port numbers, through the information line 1429-1.

[0034]FIG. 9 shows a function of the relay control section 1423 withinthe relay gateway 1401 by separating the communication function layer.The signal unit 1451 forwarded from the control communication line 1415is connected to an MTP as a communication function layer on the commonchannel signaling system. The communication function layer 1423-1 dealswith the communication processing concerning a destination point codeDPC-1, source point code OPC-1 and signaling link selection SLS-1 of inthe signal unit 1451. The communication function layer 1423-2 deals withthe communication processing concerning a message IAM, circuitidentification code CIC-1 and parameter Para-1 of in the signal unit1451. On the other hand, the communication function layer 1423-3 dealswith the communication processing concerning a destination IP addressD-adx and source IP address S-adx contained in the IP packet 1452. Thecommunication function layer 1423-4 deals with the communicationprocessing concerning a message IAM and circuit identification codeCIC-x of in the IP packet 1452.

[0035] As in the above, the gist lies in that the communication functionlayers 1423-2 and 1423-4 carry out a mutual conversion of between thepacket 1451 on the common channel signaling system and a packet 1452conforming to a rule in the prior patent application.

[0036] <<Outline of Multicast>>

[0037] Next, explanation is made on a multicast-type IP network 27-1 fora transfer of from one source of delivery to a plurality ofdestinations, with reference to FIG. 10.

[0038] Routers 27-11 to 27-20 respectively hold multicast tables. An IPpacket 29-1 having a multicast address “MA1” is sent from an IP terminalunit 28-1 to reach the router 27-18 via the router 27-11. By makingreference to a router-dependent multicast table held in the router27-18, an IP packet 29-3 and IP packet 29-4 are transferred onto acommunication line. The IP packet 29-3 is copied in the router 27-17 andturned into IP packets 29-5 and 29-6, while the IP packet 29-5 is copiedin the router 27-12 and turned into IP packets 29-8 and 29-9, respectiveof which reach an IP terminal unit 28-2 and an IP terminal unit 28-3.The IP packet 29-6 is copied in the router 27-13 and turned into an IPpacket 29-10 and 29-11, respective of which reach IP terminal units 28-4and 28-5. The IP packet 29-4 passes the routers 27-19, 27-14, and copiedIP packets 29-12 and 29-13 respectively reach IP terminal units 28-6 and28-7.

[0039] Incidentally, known is the method of transferring multicast databy storing it in a UPD segment of in an IP packet, which is applicableto the foregoing multicast. The routers 27-11 to 27-14 shown in FIG. 10are network node units. In the technique disclosed in Embodiment 18 ofthe prior patent application, an address of a terminal unit ispreviously registered in an address management table of a network nodeunit so that, by the means for examining an address included incommunicated multicast data, realized is a multicast IP-packetcommunication capable of preventing against not-allowed transmission ofmulticast data thereby enhancing information security and imposingmulticast data fee onto the recipient.

[0040] <<Example of Multicast Communication>>

[0041] This is an example disclosed as Embodiment 20 in the prior patentapplication. Explanation will be made with reference to FIG. 11. Withinan IP network 31-1, there are provided a range 31-2 under the managementof communication company X and a range 31-3 under the management ofcommunication company Y, network node units 32-1 to 32-12, routers 34-1to 34-11, and a router 34-12. The network node units and the routers areconnected directly by IP communication lines or indirectly through thenetwork node units and routers. The terminal units 33-1 to 33-17 havingan IP packet transmitting/receiving function are connected to thenetwork node units via IP communication lines. Numerals 33-24 to 33-27are multicast P service proxy servers, numerals 33-28 to 33-31 aremulticast Q service proxy servers, and numerals 33-32 to 33-35 areoverflow communication line servers. The communication companies X and Yjointly manage the routers 34-12. A multicast system with IPencapsulation is disclosed in the Embodiment 17 in the proceedingpatent.

[0042] <<Transmission Terminal Units and Transmission Management Serversof Communication Company>>

[0043] The electronic newspaper distribution service by a newspapercompany A is classified as multicast P service and the news distributionservice by a broadcasting station B is as multicast Q service. Theterminal unit 33-1 is a multicast data transmitting terminal unit underthe management of the communication company X, the terminal unit 33-2 isa transmission management server under the management of thecommunication company X, a terminal unit 33-4 is a multicast datatransmitting terminal unit under the management of the communicationcompany Y, a terminal unit 33-6 is a transmission management serverunder the management of the communication company Y, and a terminal unit33-7 is a terminal unit under the management of the newspaper company Awhich is a terminal unit for multicast P service to transmit anelectronic newspaper prepared by the newspaper company A to thetransmission management server 33-2 of the communication company X andto the transmission management server 33-6 of the communication companyY thus effecting the administrative correspondence communicationconcerning electronic newspaper distribution. A terminal unit 33-3 is aterminal unit under the management of the broadcasting station B, whichis a terminal unit for multicast Q service to transmit the (voice-movingimage) TV news distribution service offered by the broadcasting stationB to the transmission management server 33-2 of the communicationcompany X and to the transmission management server 33-6 of thecommunication company Y thus effecting the administrative correspondencecommunication concerning electronic newspaper distribution. Thetransmission management server 33-2 carries out an administrationprocedure concerning multicast data transmission, such as distributingan electronic newspaper prepared by the newspaper company A on behalf ofthe communication company X, TV news distribution service by thebroadcasting station B and electronic stock-price guide service by astock company C. Similarly, the transmission management server 33-6carries out an administration procedure concerning multicast datatransmission on behalf of the communication company Y.

[0044] <<Data Distribution via Multicast Service Proxy Server>>

[0045] Furthermore, the prior patent discloses a multicast techniquehaving an intervening multicast service proxy server, which will beexplained in the below (see FIG. 325 of the prior patent). Disclosed isa technique that the multicast data forwarded from the transmissionterminal and transferred into the IP transfer network, reaches amulticast service proxy server set up on a reception side, the multicastservice proxy server receiving the multicast data, the multicast serviceproxy server then transmitting the multicast data toward a plurality ofterminal units connected to a network node unit -by the use of amulticast data distribution function of within the network node unit,the terminal units in plurality receiving the multicast data.

[0046] <<Mobile Terminal Unit>>

[0047] The prior patent application discloses a technique ofcommunication from a mobile terminal unit through a radio communicationpath. This will be outlined with reference to FIG. 12. Text data isforwarded from an IP terminal unit 128-1 to reach a radiotransmitting/receiving section 123 of within an IP transfer network 120by way of a radio interface converting section 129-1, a radiotransmitting/receiving section 127 and a radio communication path 125,and to reach a network node unit 121 via a gateway 122, beingtransferred within the IP transfer network 120 to reach another terminalunit via another network node unit. The digital voice forwarded from anIP telephone set 128-2, similarly, reaches another telephone set via theIP transfer network. An IP voice image unit 128-3 also is similar to theabove, and voice and image data reach another IP voice image unit viathe IP transfer network.

[0048] <<Telephone Communication via Media Router>>

[0049] The prior patent application discloses a technique of telephonecommunication via a media router, which will be explained with referenceto FIGS. 13 and 14. In this example, a media router 1021 has an IPaddress “EA1” and a media router 1022 has an IP address “EA2”. Digitalvoice is stored in an IP packet given with a local IP address andforwarded from a telephone set 1011 to reach the media router 1021.Next, the media router 1021 turns into an external IP packet having asource address “EA1” and destination address “EA2”. The external IPpacket reaches a network node unit 1031 via a communication line 1040.This turns into an internal packet by the use of a first-lined record ofan address management table 1034. The internal packet is transferredwithin the IP network to reach a network node unit 1032. The internalpacket is decapsulated and the external IP packet is restored. Thispasses a communication line 1041 to reach a media router 1022 where itis stored in an IP packet given with a local IP address, thus reaching atelephone set 1012.

[0050] Next, with reference to FIG. 15, shown is another disclosureexample of another media router 1021-1. This is an example that aconnection control section 1080-1 has an external address “EA1”. Thevoice, forwarded from a telephone set 1011-1 having a telephone number“Tel-No-1”, passes a pin number “T1” at an end of a communication lineto reach a telephone control section 1081-1. The connection controlsection 1080-1 makes reference to a first-lined record “Tel-No-1, T1,5004” of a telephone number/pin number/UDP port number correspondencetable 1083 in an inside thereof to adopt a port number “5004”, and formsan external packet storing a voice having a source address “EA1” and aport number “5004” of a UDP or TCP packet within an IP packet. Namely,the media router 1021-1 is characterized by a technique that an externaladdress “EA1” and port number “5004” is assigned to a telephone sethaving a telephone number “Tel-No-1”.

[0051] Next, with reference to FIG. 16, shown is another disclosureexample of another media router 1021-2. The media router 1021-2 includesa telephone control section 1081-2, a PBX control section 1085-1, aconnection control section 1080-2, routers 1086, 1087. An IP packet,forwarded from a terminal unit 1090 of within a LAN 1093, reaches anetwork node unit of within the IP network by way of a router 1087, acommunication line 1089, a router 1086 and a communication line 1040-2.Similarly, an IP packet containing the same image data, forwarded from amoving-image transceiver 1092, reaches a network node unit of within theIP transfer network by way of a router 1087, a communication line 1089,a router 1086 and a communication line 1040-2. It is possible totransfer an IP packet in a reverse direction.

[0052] In order for implementing IP full service using an IP network,there is no terminal-to-terminal communication connection control methodfor a common carrier to provide IP full service, i.e., (1)terminal-to-terminal communication connection control method using amobile communication network and IP network, (2) method for implementingline-connection control in a level above a TCP layer, using telephonenumbers, (3) method for implementing TV conference communication usingIP-network multicast function, (4) method of configuring a relay gatewayunit for connecting an IP network and a PSTN, (5) method of setting anentire or part of an external address in an internal-packet addressarea, (6) method of setting an entire or part of an external address inan internal frame, (7) method of implementing various functions ofnetwork node units within an IP network, (8) method of carrying outfixed telephone, mobile phone and multimedia communications on the sameIP network, (9) method of implementing security ASP, (10) method oftransmitting and receiving multicast data without distinction betweenmobile and fixed terminal units, (11) method of switching a radio basepoint during voice communication, and so on.

SUMMARY OF THE INVENTION

[0053] It is an object of the present invention to resolve the problemsof and stemmed from the foregoing methods. Namely, (1) an object is tosolve the terminal-to-terminal communication connection control methodfor telephone and voice image communications in order for a mobile phoneor voice image unit to communicate with another telephone set or voiceimage unit via an IP network and a mobile communication network, (2) anobject is to solve the terminal-to-terminal communication connectioncontrol method by establishing a TCP communication path between asource-sided telephone management server and a destination-sidedtelephone management server, and then establishing a communication pathfor terminal-to-terminal communication, to thereafter carry out a voiceimage communication via an IP network between two voice image units, (3)an object is to solve or the method of implementing TV conference withIP multicast by setting a multicast communication record in an addressmanagement table of in a network node unit and setting a multicast routetable in a router, to transmit voice moving images by the use ofmulticast addresses, (4) an object is to solve the gateway configuringmethod for connecting the common channel signaling system based IPnetwork and a PSTN by installing relay gateways within an IP network inorder to effect telephone communication of telephone-IPnetwork-PSTN-telephone, (5) an object is to solve the method ofstructuring an IP network by, in IP packet encapsulation, setting anentire or part of an external address to an address area of in theinternal packet due to a method of setting within an external IP packet,(6) an object is to solve the method of structuring an IP network by amethod of setting an entire or part of an external address to an addressarea of in the internal frame, (7) an object is to solve the method ofstructuring a security IP network by implementing a method to separatean IP network into a plurality of internal IP networks by the use ofpacket filters, priority control function, multicast recipient addressconversion function and port numbers, a method to separate an IP networkinto a plurality of internal IP networks, (8) an object is to solve themethod of implementing fixed telephone and mobile phone communicationson the same IP network by the use of a CIC management table including anadministration function of a terminal-unit-sided UNI, (9) an object isto provide an IP network for implementing security ASP due to selectingan IP address, port number and protocol kind of an IP packet to becommunicated between an ASP operation server and a user program by thenetwork node unit thereby excluding non-designated IP packets, (10) anobject is to solve the multicast data method of providing IP packetexchange service (Intranet, Extranet) and fixed telephone and mobilephone services, without distinction between mobile and fixed terminalunits, on IP networks based on the same principle, and (11) an object isto solve the method for registering and changing a whereabouts positionof a telephone set by registering a mobile phone over anIP-network-formed mobile communication network in order for implementingmobile phone communication.

[0054] The present invention concerns a terminal-to-terminalcommunication connection control method using an IP network. Theforegoing object of the invention is achieved by: in order for a mobiletelephone set to have a telephone communication with a telephone set byway of a mobile communication network and an IP network, the mobilecommunication network carries out a line connection control based on thecommon channel signaling system; the IP network establishing acommunication path by transmitting and receiving a line connectioncontrol message applying the common channel signaling system to the IPnetwork thereby effecting a telephone communication.

[0055] Meanwhile, the foregoing object of the present is achieved by: inorder for a voice image unit 1 to have a voice image communication witha voice image unit 2 by way of a mobile communication network and an IPnetwork, the mobile communication network carries out a line connectioncontrol based on the common channel signaling system; the IP networkestablishing a communication path by a line connection control messageapplying the common channel signaling system to the IP network, andthereafter carrying out a control procedure for opening a voice imagecommunication path between the voice image units 1 and 2 to effect avoice image communication between the voice image units 1 and 2; whenthe voice image communication ends, the voice image units 1 and 2carrying out a control procedure for closing the voice imagecommunication path; whereby the voice image units 1 and 2 release thecommunication path according to a line-connection control message, orotherwise, by: establishing previously a TCP communication pathestablishing between a source-sided telephone management server and adestination-sided telephone management server; transmitting andreceiving circuit connection control messages IAM, ACM, CPG, ANM toestablish a communication path for terminal-to-terminal communication,and thereafter communicating voice and data between two terminal units;communicating line connection control messages REL, RLC between thesource-sided telephone management server and the destination-sidedtelephone management server to release the communication path therebyreleasing the TCP communication path.

[0056] Furthermore, achievement is by: establishing a TCP communicationpath between a source-sided telephone management server and adestination-sided telephone management server; thereafter transmittingand receiving circuit connection control messages IAM, ACM, CPG, ANM toestablish a communication path for terminal-to-terminal communication,and thereafter releasing the TCP communication path; communicating voiceand data between two terminal units; when one of the terminal units endsdata communication, establishing the TCP communication path between thesource-sided telephone management server and the destination-sidedtelephone management server; thereafter communicating line connectioncontrol messages REL, RLC to release the communication path forterminal-to-terminal communication and release the TCP communicationpath.

[0057] The present invention concerns a TV conference communicationmethod using an IP network. The foregoing object of the presentinvention is achieved by: setting an address management table in anetwork node unit, and setting a route table for multicast IP packettransfer in a router of within an IP network; a sender 1 sending a voiceand moving image by using a multicast address M1, one or more receiversreceiving the voice and moving image by using the multicast address M1;a sender 2 sending a voice and moving image by using a multicast addressM2, one or more receivers receiving the voice and moving image by usingthe multicast address M2; an IP packet being encapsulated by the addressmanagement table and transferred within the IP network to use themulticast transmission/reception function.

[0058] Meanwhile, the present invention concerns a gateway configurationwithin an IP network. The foregoing object of the present invention isachieved by: configuring a relay gateway by a relay control section anda voice control section in order to carry out a communication betweentelephone sets by way of a telephone set 1—IP network-PSTN-telephone set2; an NNI interface section based on the common channel signaling systemfor connection to a PSTN or mobile communication network being providedwithin the relay control section while a UNI interface section based onthe common channel signaling system for connection to a PSTN or mobilecommunication network being within the voice control section.

[0059] Meanwhile, the present invention concerns an IP network. Theforegoing object of the present invention is achieved by: an external IPpacket being converted into an internal packet in an input-sided networknode unit and transferred within an IP network; the external IP packetbeing to be restored from the internal packet in an output-sided networknode unit; under the control of a record of an address management tableof within the input-sided network node unit, an entire or part of anexternal address set in the external IP packet to be set to an addressarea of the internal packet.

[0060] Meanwhile, the present invention concerns an IP network. Theforegoing object of the present invention is achieved by: under thecontrol of a record of an address management table of within theinput-sided network node unit of the external IP packet, an externaladdress set in the external IP packet in an entirety or a part being tobe set to an address area of the internal frame.

[0061] Meanwhile, the present invention concerns a method for carryingout various functions of the network node unit of within the IP network.The foregoing object of the present invention is achieved by:configuring the network node unit to include at least one of a protocolfilter function and a port filter function; the protocol filter functioncontrolling, as a function upon transmission, whether to convert theexternal IP packet into an internal packet or not according to aprotocol of within the external IP packet to be inputted. Also, the portfilter function receives the internal IP packet from the inside of theIP network as a function at the destination, restores an external IPpacket from the internal IP packet and controls whether to forward itonto an external communication line according to a port number of anexternal IP packet included in a payload section in the internal IPpacket to be inputted.

[0062] The packet filter function of the network node unit includes aprotocol filter using a protocol kind of within an IP packet, and a portfilter function using a port number of within a TCP or UDP segment in anIP packet. The port filter, also, allows a packet to pass or preventsthe packet according to a port passage condition of the external IPpacket entering the network node unit. The network node unit hasfurthermore a function to convert a destination multicast IP addressinto another IP address (multicast NAT function) by the use of amulticast control table. By using the port filter applicable for acommunication record of a unit control table of within the network nodeunit, the IP network can be separated into a plurality of internalnetworks. The network node unit includes a unit control table. Thecontrol table includes a filtering control table, a packet prioritycontrol table, a multicast control table and a signature control table.The unit control table is achieved by including an address managementtable function due to the foregoing other technique.

[0063] Meanwhile, the present invention concerns an IP network. Theforegoing object of the present invention is achieved by resolving therespective of six communication cases, i.e., a communication between afixed telephone set and a fixed telephone set as Communication Case 1, acommunication between a mobile phone and a mobile phone as CommunicationCase 2, a communication between a mobile phone and a fixed telephone setas Communication Case 3, a communication between a fixed telephone setand a mobile phone as Communication Case 4, a multimediaterminal-to-terminal communication based on the common channel signalingsystem as Communication Case 5, and a multimedia terminal-to-terminalcommunication set a communication record as Communication Case 6.

[0064] The communication procedure of between the media router and thetelephone management server and the communication procedure of betweenthe media router and the telephone management server are UNIs. Thecommunication procedure of between the telephone management server andthe telephone management server is an NNI based on the common channelsignaling system. The IP network includes two or more network nodeunits. An external packet forwarded from a media router 1 or radio basepoint 1 turns into an internal packet in a source-sided network nodeunit. The internal packet is transferred within the communicationnetwork. The internal packet is restored into an external packet in adestination-sided network node unit and forwarded to a media router 2 orradio base point 2.

[0065] In Communication Case 1 to Communication Case 4, a communicationis made connecting, from a communication line, a terminal unit 1, amedia router 1 or radio base point 1, a telephone management server 1, atelephone management server 2, a media router 2 or radio base point 2and a terminal unit 2. Accordingly, the communication procedure ofbetween the media router or radio base point and the telephonemanagement server is an UNI for the media router or radio base pointwhile the communication procedure of between the telephone managementserver and the telephone management server is an NNI based on the commonchannel signaling system. By the above noted method, theterminal-to-terminal communication connection control method is carriedout. The radio base point includes an IP communication line interfacesection, radio interface section and a radio transmitting/receivingsection, making possible telephone communication with any of an analogmobile phone, a digital mobile phone and IP movement. Also, theforegoing object is achieved by using a channel-IP addresscorrespondence table to enable the management of the IP addresses to beused by the mobile phone.

[0066] In Communication Case 5, a communication is made connecting, froma communication line, a multimedia terminal unit 1, a media router 1 orradio base point 1, a telephone management server 1, a telephonemanagement server 2, a media router 2 or the radio base point 2 and amultimedia terminal unit 2. Accordingly, the communication procedure ofbetween the telephone management server and the telephone managementserver carries out an NNI based on the common channel signaling system,thereby achieving the forgoing object. In Communication Case 6, acommunication is made connecting, from a communication line, an IPterminal unit 1 having an IP packet transmission/reception function, amedia router 1 or radio base point 1, a telephone management server 1, atelephone management server 2, a media router 2 or the radio base point2 and an IP terminal unit 2. Similarly to the above, the communicationprocedure of between the telephone management server and the telephonemanagement server does not employ the common channel signaling system.Furthermore, a communication record is set within a unit control tablein order for use in a communication between the IP terminal 1 and the IPterminal 2 on the basis of a request by the IP terminal 1. Thecommunication record is deleted after closing the communication, therebyachieving the foregoing object.

[0067] Meanwhile, the present invention concerns an IP network. In theforegoing object of the present invention, a mobile phone for carryingout a mobile telephone communication is registered to a mobile networkcomprising an IP network; while the mobile phone 1 is continuing atelephone communication by way of a communication line of the mobilephone 1—a radio base point 1—telephone management server 1—a telephonemanagement server 2—radio base point 2—mobile phone 2, the mobile phone1 can move in geographical position to communicate with another radiobase point 3, i.e. can continue the telephone communication by way of acommunication line of the mobile phone 1—radio base point 3—telephonemanagement server 1—telephone management server 2—radio base point2—mobile phone 2. Furthermore, achievement is made by solving a methodthat, while the mobile phone 1 is continuing a telephone communicationby way of a communication line of the mobile phone 1—radio base point1—telephone management server 1 telephone management server 2—radio basepoint 2—mobile phone 2, the mobile phone 1 can move to another radiobase point 4 under the administration of a telephone management server4, i.e. continues the telephone communication by way of a communicationline of the mobile phone 1—radio base point 4—telephone managementserver 4—telephone management server 2—radio base point 2—mobile phone2.

[0068] Meanwhile, the present invention concerns an ASP service realizedthrough an IP network. The foregoing object of the present invention isachieved by: the network node unit selects an IP address, port number orprotocol kind of an IP packet communicated between an ASP server and auser program to exclude the other IP packet than that designated wherebyan IP packet containing a permitted IP address, port number or protocolkind passes the network node unit while the IP packet not allowed isexcluded in the network node unit thereby making possible to carry outan IP network capable of providing security ASP service.

[0069] Meanwhile, the present invention concerns an IP network. Theforegoing object of the present invention is achieved by: in order totransmit multicast data to nearly all the network node units of withinthe IP network and receive the multicast data by a plurality of mobileterminal units, a mobile terminal unit carries out a terminal-unitauthentication communication procedure to a radio base point so that themobile terminal unit allowed receives the multicast data.

BRIEF DESCRIPTION OF THE DRAWINGS

[0070] In the accompanying drawings:

[0071]FIG. 1 is a figure explaining a conventional encapsulationtechnique for an IP packet;

[0072]FIG. 2 is a figure explaining a conventional simplifiedencapsulation technique for an IP packet;

[0073]FIG. 3 is a figure explaining a conventional method for operatingan address management table of within a network node unit from a userterminal unit;

[0074]FIG. 4 is a figure explaining a conventional technique that aconversion table server accesses a domain name server;

[0075]FIG. 5 is a figure explaining a hierarchical structure of aconventional communication function when a common channel signalingsystem is applied to an IP network;

[0076]FIG. 6 is a figure explaining a conventional IP network employinga common channel signaling system;

[0077]FIG. 7 is a figure explaining a conventional concept applying acommon channel signaling system to an IP network;

[0078]FIG. 8 is a figure explaining a conventional connection control ofa telephone set applied with a common channel signaling system;

[0079]FIG. 9 is a figure for explaining a gateway logic structure of aprior patent application centering on line connection control;

[0080]FIG. 10 is a view explaining the conventional packet transfer bymulticast;

[0081]FIG. 11 is a figure explaining the conventional packet transfer bymulticast;

[0082]FIG. 12 is a figure explaining a conventional concept ofcommunication via a radio communication path from a mobile terminalunit;

[0083]FIG. 13 is a figure explaining a conventional concept concerningtelephone communication via a media router;

[0084]FIG. 14 is a figure explaining a conventional concept concerningtelephone communication via a media router;

[0085]FIG. 15 is a figure explaining a conventional concept concerningmedia router configuration;

[0086]FIG. 16 is a figure explaining a conventional concept concerningmedia router configuration;

[0087]FIG. 17 is a figure explaining a communication between a mobilecommunication network and an IP network, in a first embodiment of thepresent invention;

[0088]FIG. 18 is a figure explaining a method of controllingterminal-to-terminal communication connection via a mobile communicationnetwork and IP network, in the first embodiment of the presentinvention;

[0089]FIG. 19 is a figure explaining an IP packet form used interminal-to-terminal communication connection control, in the firstembodiment of the present invention;

[0090]FIG. 20 is a figure explaining an IP packet form used interminal-to-terminal communication connection control, in the firstembodiment of the invention;

[0091]FIG. 21 is a figure explaining an IP packet form used interminal-to-terminal communication connection control, in the firstembodiment of the present invention;

[0092]FIG. 22 is a figure explaining an IP packet form used interminal-to-terminal communication connection control, in the firstembodiment of the present invention;

[0093]FIG. 23 is a figure explaining an IP packet form used interminal-to-terminal communication connection control, in the firstembodiment of the present invention;

[0094]FIG. 24 is a figure explaining an IP packet form used interminal-to-terminal communication connection control, in the firstembodiment of the present invention;

[0095]FIG. 25 is a figure explaining an IP packet form used interminal-to-terminal communication connection control, in the firstembodiment of the present invention;

[0096]FIG. 26 is a figure explaining an IP packet form used interminal-to-terminal communication connection control, in the firstembodiment of the present invention;

[0097]FIG. 27 is a figure explaining a method of controllingterminal-to-terminal communication connection via a mobile communicationnetwork and IP network, in the first embodiment of the presentinvention;

[0098]FIG. 28 is a figure explaining the communication between a mobilecommunication network and an IP network, in a first embodiment of thepresent invention;

[0099]FIG. 29 is a figure explaining a method of controllingterminal-to-terminal communication connection via a mobile communicationnetwork and IP network, in the first embodiment of the presentinvention;

[0100]FIG. 30 is a figure explaining a communication-functionhierarchical structure, in a second embodiment of the present invention;

[0101]FIG. 31 is a figure explaining an application method of TCPtechnique, in the second embodiment of the present invention;

[0102]FIG. 32 is a figure explaining the application method of TCPtechnique, in the second embodiment of the present invention;

[0103]FIG. 33 is a figure explaining a communication via an IP networkbetween two terminal units, in the second embodiment of the presentinvention;

[0104]FIG. 34 is a figure explaining a circuit connection control in aTCP session, in the second embodiment of the present invention;

[0105]FIG. 35 is a figure explaining a TCP header form, in the secondembodiment of the present invention;

[0106]FIG. 36 is a figure explaining an IP network applied with amulticast technique, in a third embodiment of the present invention;

[0107]FIG. 37 is a figure explaining the multicast technique, in thethird embodiment of the present invention;

[0108]FIG. 38 is a figure explaining the multicast technique, in thethird embodiment of the present invention;

[0109]FIG. 39 is a figure explaining the multicast technique, in thethird embodiment of the present invention;

[0110]FIG. 40 is a figure explaining a manner of multicast packettransfer by the multicast technique, in the third embodiment of thepresent invention;

[0111]FIG. 41 is a figure explaining a manner of multicast packettransfer by the multicast technique, in the third embodiment of thepresent invention;

[0112]FIG. 42 is a figure explaining a manner of multicast packettransfer by the multicast technique, in the third embodiment of thepresent invention;

[0113]FIG. 43 is a figure explaining a relay gateway configuration, in afourth embodiment of the present invention;

[0114]FIG. 44 is a figure explaining a relay gateway configuration, inthe fourth embodiment of the present invention;

[0115]FIG. 45 is a figure explaining a manner of IP packet transfer viaan IP network, in a fifth embodiment of the present invention;

[0116]FIG. 46 is a figure explaining a correspondence between a 28-bitlength address and a 128-bit length address, in the fifth embodiment ofthe present invention;

[0117]FIG. 47 is a figure explaining a relationship between an externalIP packet and an internal packet, in the fifth embodiment of the presentinvention;

[0118]FIG. 48 is a figure explaining a relationship between an externalIP packet and an internal packet, in the fifth embodiment of the presentinvention;

[0119]FIG. 49 is a figure explaining a correspondence between a 28-bitlength address and a 128-bit length address, in the fifth embodiment ofthe present invention;

[0120]FIG. 50 is a figure explaining a correspondence between a 28-bitlength address and a 128-bit length address, in the fifth embodiment ofthe present invention;

[0121]FIG. 51 is a figure explaining a relationship between an externalIP packet and an internal packet, in the fifth embodiment of the presentinvention;

[0122]FIG. 52 is a figure explaining a relationship between an externalIP packet and an internal packet, in the fifth embodiment of the presentinvention;

[0123]FIG. 53 is a figure explaining a relationship between an externalIP packet and an internal packet, in the fifth embodiment of the presentinvention;

[0124]FIG. 54 is a figure explaining a manner of IP packet transfer viaan IP network, in a sixth embodiment of the present invention;

[0125]FIG. 55 is a figure explaining a relationship between an externalIP packet and an internal frame, in the sixth embodiment of the presentinvention;

[0126]FIG. 56 is a figure explaining a relationship between an externalIP packet and an internal frame, in the sixth embodiment of the presentinvention;

[0127]FIG. 57 is a figure explaining a relationship between an externalIP packet and an internal frame, in the sixth embodiment of the presentinvention;

[0128]FIG. 58 is a figure explaining a relationship between an externalIP packet and an internal frame, in the sixth embodiment of the presentinvention;

[0129]FIG. 59 is a figure explaining a relationship between acommunication network and network node units, in a seventh embodiment ofthe present invention;

[0130]FIG. 60 is a figure explaining a relationship between an IPnetwork and network node units, in the seventh embodiment of the presentinvention;

[0131]FIG. 61 is a figure explaining a relationship between the networknode unit and the terminal unit gateway appearing in another embodimentor the prior patent application, in the seventh embodiment of thepresent invention;

[0132]FIG. 62 is a figure showing a communication record, in the seventhembodiment of the present invention;

[0133]FIG. 63 is a figure of a communication record represented in aprogram language C, in the seventh embodiment of the present invention;

[0134]FIG. 64 is an example of a unit conversion table comprising aplurality of communication record, in the seventh embodiment of thepresent invention;

[0135]FIG. 65 is a figure representing a process flow of the networknode unit at transmission, in the seventh embodiment of the presentinvention;

[0136]FIG. 66 is a figure representing a process flow of the networknode unit at reception, in the seventh embodiment of the presentinvention;

[0137]FIG. 67 is a figure explaining on how to make reference from amain table to a sub-table, in the seventh embodiment of the presentinvention;

[0138]FIG. 68 is a figure representing a protocol filter control recordform, in the seventh embodiment of the present invention;

[0139]FIG. 69 is a figure representing a port filter control recordform, in the seventh embodiment of the present invention;

[0140]FIG. 70 is a figure explaining the overall flow of packet prioritycontrol, in the seventh embodiment of the present invention;

[0141]FIG. 71 is a figure representing a priority control record form,in the seventh embodiment of the present invention;

[0142]FIG. 72 is a figure of a priority control record represented in aprogram language C, in the seventh embodiment of the present invention;

[0143]FIG. 73 is a figure showing an example of a plurality of prioritycontrol records, in the seventh embodiment of the present invention;

[0144]FIG. 74 is a figure explaining the overall flow of multicast, inthe seventh embodiment of the present invention;

[0145]FIG. 75 is a figure showing an example of a multicast controlrecord, in the seventh embodiment of the present invention;

[0146]FIG. 76 is a figure showing another example of a multicast controlrecord, in the seventh embodiment of the present invention;

[0147]FIG. 77 is a figure explaining overflow line control in multicast,in the seventh embodiment of the present invention;

[0148]FIG. 78 is a figure showing another example of a multicast controlrecord, in the seventh embodiment of the present invention;

[0149]FIG. 79 is a figure showing a multicast control function—2, in theseventh embodiment of the present invention;

[0150]FIG. 80 is a figure showing a form 4 of a second multicast controlrecord used for carrying out the multicast control function—2, in theseventh embodiment of the present invention;

[0151]FIG. 81 is an example of a unit control table comprising aplurality of communication record used for carrying out the multicastcontrol function—2, in the seventh embodiment of the present invention;

[0152]FIG. 82 is a figure explaining a procedure of transmitting andreceiving multicast data in the multicast control function—2, in theseventh embodiment of the present invention;

[0153]FIG. 83 is a figure explaining on how to report a reception in themulticast control function—2, in the seventh embodiment of the presentinvention;

[0154]FIG. 84 is a figure explaining the overall flow of electronicsignature, in the seventh embodiment of the present invention;

[0155]FIG. 85 is a figure showing an electronic signature control recordform, in the seventh embodiment of the present invention;

[0156]FIG. 86 is a figure explaining on how to separate the IP networkinto a plurality of internal IP networks, in the seventh embodiment ofthe present invention;

[0157]FIG. 87 is a figure explaining a function of the unit controltable for separating the IP network into a plurality of internal IPnetworks, in the seventh embodiment of the present invention;

[0158]FIG. 88 is a figure explaining another method for finding outvarious control records from a communication record, in the seventhembodiment of the present invention;

[0159]FIG. 89 is a figure explaining still another method for findingout various control records from a communication record, in the seventhembodiment of the present invention;

[0160]FIG. 90 is a figure showing another form of a communicationrecord, in the seventh embodiment of the present invention;

[0161]FIG. 91 is a figure showing an example that an external packet isconverted into an IPv6-formed internal packet and transferred, in theseventh embodiment of the present invention;

[0162]FIG. 92 is an example of an IPv6-formed internal packet, in theseventh embodiment of the present invention;

[0163]FIG. 93 is a figure showing a form of a communication record as anIPv6-formed internal packet, in the seventh embodiment of the presentinvention;

[0164]FIG. 94 is a figure showing an example that an external IP packetis converted into a MAC-formed internal frame and transferred, in theseventh embodiment of the present invention;

[0165]FIG. 95 is an example of a MAC-formed internal frame, in theseventh embodiment of the present invention;

[0166]FIG. 96 is a figure showing a form of a communication record as anexample of a MAC-formed internal frame, in the seventh embodiment of thepresent invention;

[0167]FIG. 97 is a figure showing an example that an internal packetformed by providing a tag to an external packet is transferred, in theseventh embodiment of the present invention;

[0168]FIG. 98 is a figure showing an example of a communication recordfor the internal packet formed by providing a tag to an external packet,in the seventh embodiment of the present invention;

[0169]FIG. 99 is a figure showing an example of conversion to andtransfer of another formed internal packet formed by providing a tag toan external packet, in the seventh embodiment of the present invention;

[0170]FIG. 100 is a figure showing an example of a communication recordfor the other formed internal packet formed by providing a tag to anexternal packet, in the seventh embodiment of the present invention;

[0171]FIG. 101 is a figure showing an example of conversion to andtransfer of a MAC frame having an extended tag, in the seventhembodiment of the present invention;

[0172]FIG. 102 is a figure explaining configurations of a MAC frame anda MAC frame having an extended tag, in the seventh embodiment of thepresent invention;

[0173]FIG. 103 is a figure showing an example of a communication recordfor a MAC frame having an extended tag, in the seventh embodiment of thepresent invention;

[0174]FIG. 104 is a figure showing an example of conversion to andtransfer of an MPLS frame, in the seventh embodiment of the presentinvention;

[0175]FIG. 105 is a figure explaining a communication record for an MPLSframe, in the seventh embodiment of the present invention;

[0176]FIG. 106 is a figure showing an example of conversion and transferof an HDLC frame, in the seventh embodiment of the present invention;

[0177]FIG. 107 is a figure explaining a communication record for an HDLCframe, in the seventh embodiment of the present invention;

[0178]FIG. 108 is a figure explaining a method for carrying out fixedtelephone communication and mobile phone communication on the same IPnetwork and further a multimedia terminal-to-terminal communicationusing a telephone number, in an eighth embodiment of the presentinvention;

[0179]FIG. 109 is a figure showing a method for carrying out acommunication from a fixed telephone set to a fixed telephone set in anIP network, in Communication Case 1 of the eighth embodiment of thepresent invention;

[0180]FIG. 110 is a figure showing an IP packet to be transferred from acalling-sided media router to a network node unit, in Communication Case1 of the eighth embodiment of the present invention;

[0181]FIG. 111 is a figure showing an IP packet to be transferred from anetwork node unit to a proxy telephone server, in Communication Case 1of the eighth embodiment of the present invention;

[0182]FIG. 112 is a figure showing an IP packet to be transferred from aproxy telephone server to a telephone management server, inCommunication Case 1 of the eighth embodiment of the present invention;

[0183]FIG. 113 is a figure showing a calling-sided CIC management table,in Communication Case 1 of the eighth embodiment of the presentinvention;

[0184]FIG. 114 is a figure showing an IP packet to be sent from atelephone management server to a telephone number server, inCommunication Case 1 of the eighth embodiment of the present invention;

[0185]FIG. 115 is a figure showing an IP packet to be sent from atelephone number server back to a telephone management server, inCommunication Case 1 of the eighth embodiment of the present invention;

[0186]FIG. 116 is another figure showing another example of acalling-sided CIC management table, in Communication Case 1 of theeighth embodiment of the present invention;

[0187]FIG. 117 is a figure showing a UNI look-up, in Communication Case1 of the eighth embodiment of the present invention;

[0188]FIG. 118 is a figure showing an IAM message to be sent from acalling-sided telephone management server to a called-sided telephonemanagement server, in Communication Case 1 of the eighth embodiment ofthe present invention;

[0189]FIG. 119 is a figure showing a reception-sided CIC managementtable, in Communication Case 1 of the eighth embodiment of the presentinvention;

[0190]FIG. 120 is a figure showing an IP packet to be transferred from atelephone management server to a proxy telephone server, inCommunication Case 1 of the eighth embodiment of the present invention;

[0191]FIG. 121 is a figure showing an IP packet to be transferred from aproxy telephone server to a network node unit, in Communication Case 1of the eighth embodiment of the present invention;

[0192]FIG. 122 is a figure showing an IP packet to be transferred from anetwork node unit to a media router, in Communication Case 1 of theeighth embodiment of the present invention;

[0193]FIG. 123 is a figure showing an ACM message to be sent from acalled-sided telephone management server to a calling-sided telephonemanagement server, in Communication Case 1 of the eighth embodiment ofthe present invention;

[0194]FIG. 124 is a figure showing an IP packet to be transferred from acalled-sided media router to a network node unit, in Communication Case1 of the eighth embodiment of the present invention;

[0195]FIG. 125 is a figure showing an IP packet to be transferred from anetwork node unit to a proxy telephone server, in Communication Case 1of the eighth embodiment of the present invention;

[0196]FIG. 126 is a figure showing an IP packet to be transferred from aproxy telephone server to a telephone management server, inCommunication Case 1 of the eighth embodiment of the present invention;

[0197]FIG. 127 is a figure showing a CPG message to be sent from acalled-sided telephone management server to a calling-sided telephonemanagement server, in Communication Case 1 of the eighth embodiment ofthe present invention;

[0198]FIG. 128 is a figure showing an IP packet to be transferred from acalling-sided telephone management server to a proxy telephone server,in Communication Case 1 of the eighth embodiment of the presentinvention;

[0199]FIG. 129 is a figure showing an IP packet to be transferred from aproxy telephone server to a network node unit, in Communication Case 1of the eighth embodiment of the present invention;

[0200]FIG. 130 is a figure showing an IP packet to be transferred from anetwork node unit to a media router, in Communication Case 1 of theeighth embodiment of the present invention;

[0201]FIG. 131 is a figure showing an ANM message to be sent from acalled-sided telephone management server to a calling-sided telephonemanagement server, in Communication Case 1 of the eighth embodiment ofthe present invention;

[0202]FIG. 132 is a figure showing an IP packet to be transferred from acalling-sided media router to a called-sided media router, inCommunication Case 1 of the eighth embodiment of the present invention;

[0203]FIG. 133 is a figure showing a state that an IP packet to betransferred from a calling-sided media router to a called-sided mediarouter has been encapsulated into an internal packet, in CommunicationCase 1 of the eighth embodiment of the present invention;

[0204]FIG. 134 is a figure showing a REL message to be sent from acalling-sided telephone management server to a called-sided telephonemanagement server, in Communication Case 1 of the eighth embodiment ofthe present invention;

[0205]FIG. 135 is a figure showing a RLC message to be sent from acalled-sided telephone management server to a calling-sided telephonemanagement server, in Communication Case 1 of the eighth embodiment ofthe present invention;

[0206]FIG. 136 is a figure showing Example 1 of the unit control table,to be used in Communication Case 1 to Communication Case 6 of the eighthembodiment of the present invention;

[0207]FIG. 137 is a figure showing Example 2 of the unit control table,to be used in Communication Case 1 to Communication Case 6 of the eighthembodiment of the present invention;

[0208]FIG. 138 is a figure showing Example 3 of the unit control table,to be used in Communication Case 1 to Communication Case 6 of the eighthembodiment of the present invention;

[0209]FIG. 139 is a figure showing Example 4 of the unit control table,to be used in Communication Case 1 to Communication Case 6 of the eighthembodiment of the present invention;

[0210]FIG. 140 is a figure showing an outgoing-call management table, tobe used in Communication Case 1 of the eighth embodiment of the presentinvention;

[0211]FIG. 141 is a figure showing an incoming-call management table, tobe used in Communication Case 1 of the eighth embodiment of the presentinvention;

[0212]FIG. 142 is a figure explaining CIC information collection by anoperation management server, in the eighth embodiment of the presentinvention;

[0213]FIG. 143 is a two-sheeted first figure showing a method forcarrying out a communication from a mobile phone to a mobile phone in anIP network, in Communication Case 1 of the eighth embodiment of thepresent invention;

[0214]FIG. 144 is a two-sheeted second figure showing a method forcarrying out a communication from a mobile phone to a mobile phone in anIP network, in Communication Case 2 of the eighth embodiment of thepresent invention;

[0215]FIG. 145 is a figure showing an IP packet to be transferred from acalling-sided radio base point to a network node unit, in CommunicationCase 2 of the eighth embodiment of the present invention;

[0216]FIG. 146 is a figure showing an IP packet to be transferred from anetwork node unit to a proxy telephone server, in Communication Case 2of the eighth embodiment of the present invention;

[0217]FIG. 147 is a figure showing an IP packet to be transferred from aproxy telephone server to a telephone management server, inCommunication Case 2 of the eighth embodiment of the present invention;

[0218]FIG. 148 is a figure showing a calling-sided CIC management table,in Communication Case 2 of the eighth embodiment of the presentinvention;

[0219]FIG. 149 is a figure showing an IP packet to be transferred from atelephone management server to a telephone number server, inCommunication Case 2 of the eighth embodiment of the present invention;

[0220]FIG. 150 is a figure showing an IP packet to be sent from atelephone number server back to a telephone management server, inCommunication Case 2 of the eighth embodiment of the present invention;

[0221]FIG. 151 is a figure showing an example of a calling-sided CICmanagement table, in Communication Case 2 of the eighth embodiment ofthe present invention;

[0222]FIG. 152 is a figure showing an example of an IP packet containingauthentication request information to be transferred from a telephonemanagement server to a telephone number server, in Communication Case 2of the eighth embodiment of the present invention;

[0223]FIG. 153 is a figure showing an example of an IP packet containingauthentication request information to be transferred from a proxytelephone server to a network node unit, in Communication Case 2 of theeighth embodiment of the present invention;

[0224]FIG. 154 is a figure showing an example of an IP packet containingauthentication request information to be transferred from a network nodeunit to a radio base point, in Communication Case 2 of the eighthembodiment of the present invention;

[0225]FIG. 155 is a figure showing an example of an IP packet containingauthentication answer information to be transferred from a radio basepoint to a network node unit, in Communication Case 2 of the eighthembodiment of the present invention;

[0226]FIG. 156 is a figure showing an example of an IP packet containingauthentication answer information to be transferred from a network nodeunit to a proxy telephone server, in Communication Case 2 of the eighthembodiment of the present invention;

[0227]FIG. 157 is a figure showing an example of an IP packet containingauthentication answer information to be transferred from a proxytelephone server to a telephone management server, in Communication Case2 of the eighth embodiment of the present invention;

[0228]FIG. 158 is a figure showing an example of an IAM message to besent from a calling-sided proxy telephone server to a called-sidedtelephone management server, in Communication Case 2 of the eighthembodiment of the present invention;

[0229]FIG. 159 is a figure showing an example of a called-sided CICmanagement table, in Communication Case 2 of the eighth embodiment ofthe present invention;

[0230]FIG. 160 is a figure showing an IP packet to be transferred from atelephone management server to a proxy telephone server, inCommunication Case 2 of the eighth embodiment of the present invention;

[0231]FIG. 161 is a figure showing an IP packet to be transferred from aproxy telephone server to a network node unit, in Communication Case 2of the eighth embodiment of the present invention;

[0232]FIG. 162 is a figure showing an IP packet to be transferred from anetwork node unit to a radio base point, in Communication Case 2 of theeighth embodiment of the present invention;

[0233]FIG. 163 is a figure showing an IP packet containingauthentication request information to be transferred from a radio basepoint to a network node unit, in Communication Case 2 of the eighthembodiment of the present invention;

[0234]FIG. 164 is a figure showing an IP packet containingauthentication request information to be transferred from a network nodeunit to a proxy telephone server, in Communication Case 2 of the eighthembodiment of the present invention;

[0235]FIG. 165 is a figure showing an IP packet containingauthentication request information to be transferred from a proxytelephone server to a telephone management server-, in CommunicationCase 2 of the eighth embodiment of the present invention;

[0236]FIG. 166 is a figure showing an IP packet containing terminal-unitauthentication correctness/incorrectness to be transferred from atelephone management server to a proxy telephone server, inCommunication Case 2 of the eighth embodiment of the present invention;

[0237]FIG. 167 is a figure showing an IP packet containing terminal-unitauthentication correctness/incorrectness to be transferred from a proxytelephone server to a network node unit, in Communication Case 2 of theeighth embodiment of the present invention;

[0238]FIG. 168 is a figure showing an IP packet containing terminal-unitauthentication correctness/incorrectness to be transferred from anetwork node unit to a radio base point, in Communication Case 2 of theeighth embodiment of the present invention;

[0239]FIG. 169 is a figure showing an ACM message to be sent from acalled-sided telephone management server to a calling-sided telephonemanagement server, in Communication Case 2 of the eighth embodiment ofthe present invention;

[0240]FIG. 170 is a figure showing an IP packet to be transferred from acalled-sided radio base point to a network node unit, in CommunicationCase 2 of the eighth embodiment of the present invention;

[0241]FIG. 171 is a figure showing an IP packet to be transferred from anetwork node unit to a proxy telephone server, in Communication Case 2of the eighth embodiment of the present invention;

[0242]FIG. 172 is a figure showing an IP packet to be transferred from aproxy telephone server to a telephone management server, inCommunication Case 2 of the eighth embodiment of the present invention;

[0243]FIG. 173 is a figure showing a CPG message to be sent from acalled-sided telephone management server to a calling-sided telephonemanagement server, in Communication Case 2 of the eighth embodiment ofthe present invention;

[0244]FIG. 174 is a figure showing an IP packet to be transferred from acalling-sided telephone management server to a proxy telephone server,in Communication Case 2 of the eighth embodiment of the presentinvention;

[0245]FIG. 175 is a figure showing an IP packet to be transferred from aproxy telephone server to a network node unit, in Communication Case 2of the eighth embodiment of the present invention;

[0246]FIG. 176 is a figure showing an IP packet to be transferred from anetwork node unit to a radio base point, in Communication Case 2 of theeighth embodiment of the present invention;

[0247]FIG. 177 is a figure showing an ANM message to be sent from acalled-sided telephone management server to a calling-sided telephonemanagement server, in Communication Case 2 of the eighth embodiment ofthe present invention;

[0248]FIG. 178 is a figure showing an IP packet to be transferred from acalling-sided radio base point to a called-sided radio base point, inCommunication Case 2 of the eighth embodiment of the present invention;

[0249]FIG. 179 is a figure showing that an IP packet to be transferredfrom a calling-sided radio base point to a called-sided radio base pointis encapsulated into an internal packet, in Communication Case 2 of theeighth embodiment of the present invention;

[0250]FIG. 180 is a figure showing an REL message to be sent from acalling-sided telephone management server to a called-sided telephonemanagement server, in Communication Case 2 of the eighth embodiment ofthe present invention;

[0251]FIG. 181 is a figure showing an RLC message to be sent from acalled-sided telephone management server to a calling-sided telephonemanagement server, in Communication Case 2 of the eighth embodiment ofthe present invention;

[0252]FIG. 182 is a figure showing a method for carrying out acommunication from a mobile phone to a fixed telephone set in an IPnetwork, in Communication Case 3 of the eighth embodiment of the presentinvention;

[0253]FIG. 183 is a figure showing a method for carrying out acommunication from a fixed telephone set to a mobile phone in an IPnetwork, in Communication Case 4 of the eighth embodiment of the presentinvention;

[0254]FIG. 184 is a figure explaining a relationship between a mobilephone and a radio base point, in Communication Case 2 to CommunicationCase 4 of the eighth embodiment of the present invention;

[0255]FIG. 185 is a figure showing an embodiment of a channel-IP addresscorrespondence table of within a radio base point, in the eighthembodiment of the present invention;

[0256]FIG. 186 is a figure showing an embodiment where a control signalor voice signal forwarded from an analog mobile phone is IP capsulatedat a radio base point and transferred, in the eighth embodiment of thepresent invention;

[0257]FIG. 187 is a figure showing a manner that an IP packet containingcontrol or voice forwarded from an IP mobile phone is transferred via aradio base point, in the eighth embodiment of the present invention;

[0258]FIG. 188 is a figure showing a manner that an IP packet containingcontrol or voice forwarded from an IP mobile phone is transferred via aradio base point, in the eighth embodiment of the present invention;

[0259]FIG. 189 is a figure showing a method for carrying out acommunication from a multimedia terminal unit to a multimedia terminalunit in an IP network, in Communication Case 5 of the eighth embodimentof the present invention;

[0260]FIG. 190 is a figure showing a relationship between a multimediaterminal unit and an IP network, in Communication Case 5 of the eighthembodiment of the present invention;

[0261]FIG. 191 is a figure showing the outline of a communication flowfrom a multimedia terminal unit to a multimedia terminal unit, inCommunication Case 5 of the eighth embodiment of the present invention;

[0262]FIG. 192 is a figure showing a protocol stack in the communicationof between multimedia terminal units, in Communication Case 5 of theeighth embodiment of the present invention;

[0263]FIG. 193 is a figure showing a communication connection procedureof between an IP terminal unit to another IP terminal unit, inCommunication Case 6 of the eighth embodiment of the present invention;

[0264]FIG. 194 is a figure showing another communication connectionprocedure of between an IP terminal unit to another IP terminal unit, inCommunication Case 6 of the eighth embodiment of the present invention;

[0265]FIG. 195 is a figure showing an IP packet to be transferred from amedia router to a network node unit, in Communication Case 6 of theeighth embodiment of the present invention;

[0266]FIG. 196 is a figure showing an IP packet to be transferred from anetwork node unit to a proxy telephone server, in Communication Case 6of the eighth embodiment of the present invention;

[0267]FIG. 197 is a figure showing an IP packet to be transferred from aproxy telephone server to a telephone management server, inCommunication Case 6 of the eighth embodiment of the present invention;

[0268]FIG. 198 is a figure showing an IP packet containing a querycontent to a telephone management server, in Communication Case 6 of theeighth embodiment of the present invention;

[0269]FIG. 199 is a figure showing an IP packet containing an answerfrom a telephone management server, in Communication Case 6 of theeighth embodiment of the present invention;

[0270]FIG. 200 is a figure showing a transmission-sided CIC managementtable, in Communication Case 6 of the eighth embodiment of the presentinvention;

[0271]FIG. 201 is a figure showing an IP packet to be transferred from atelephone management server to another telephone management server, inCommunication Case 6 of the eighth embodiment of the present invention;

[0272]FIG. 202 is a figure showing a reception-sided CIC managementtable, in Communication Case 6 of the eighth embodiment of the presentinvention;

[0273]FIG. 203 is a figure showing an IP packet to be transferred from atelephone management server to a proxy telephone server, inCommunication Case 6 of the eighth embodiment of the present invention;

[0274]FIG. 204 is a figure showing an IP packet to be transferred from aproxy telephone server to a network node unit, in Communication Case 6of the eighth embodiment of the present invention;

[0275]FIG. 205 is a figure showing an IP packet to be transferred from anetwork node unit to a media router, in Communication Case 6 of theeighth embodiment of the present invention;

[0276]FIG. 206 is a figure showing an IP packet to be transferred froman IP terminal to another IP terminal, in Communication Case 6 of theeighth embodiment of the present invention;

[0277]FIG. 207 is a figure showing an internal packet formed from anexternal IP packet forwarded from an IP terminal, in Communication Case6 of the eighth embodiment of the present invention;

[0278]FIG. 208 is a figure explaining a registration procedure of afixed telephone set, in Communication Case 1 of the eighth embodiment ofthe present invention;

[0279]FIG. 209 is a figure explaining an information exchange betweentelephone number servers, in the eighth embodiment of the presentinvention;

[0280]FIG. 210 is another figure explaining an information exchangeprocedure between telephone number servers, in the eighth embodiment ofthe present invention;

[0281]FIG. 211 is a figure explaining a registration procedure of amobile phone, in Communication Case 2 of the eighth embodiment of thepresent invention;

[0282]FIG. 212 is a figure showing one of the external packets to beused in Communication Case 2 of the eighth embodiment of the presentinvention;

[0283]FIG. 213 is a figure showing one of the internal packets to beused in Communication Case 2 of the eighth embodiment of the presentinvention;

[0284]FIG. 214 is a figure explaining a position change procedure of amobile phone, in the eighth embodiment of the present invention;

[0285]FIG. 215 is a figure explaining another registration procedure ofa mobile phone, in the eighth embodiment of the present invention;

[0286]FIG. 216 is a figure explaining another position change procedureof a mobile phone, in the eighth embodiment of the present invention;

[0287]FIG. 217 is a figure showing a position, in the IP network, of aroute telephone number server to be introduced when the scale of the IPnetwork increases, in the eighth embodiment of the present invention;

[0288]FIG. 218 is a figure showing a communication between a routetelephone number server and a superior telephone number server, in theeighth embodiment of the present invention;

[0289]FIG. 219 is a figure showing that communication is possiblebetween route telephone number servers and superior telephone numberservers, in the eighth embodiment of the present invention;

[0290]FIG. 220 is a figure explaining a method for obtaining an IPaddress via a superior telephone number server when a destinationtelephone set is a fixed telephone set, in the eighth embodiment of thepresent invention;

[0291]FIG. 221 is a figure explaining a method for obtaining an IPaddress via a superior telephone number server when a destinationtelephone set is a mobile phone, in the eighth embodiment of the presentinvention;

[0292]FIG. 222 is a figure showing an example of a communication recordnot for encapsulation in a network node unit, in a seventh embodiment ofthe present invention;

[0293]FIG. 223 is a figure showing an example of communication that aninternal packet is the same as an external packet, in the seventhembodiment of the present invention;

[0294]FIG. 224 is a figure explaining a method for carrying out ASPservice, in a ninth embodiment of the present invention;

[0295]FIG. 225 is a figure showing an embodiment of a protocol controlrecord and port control record, in the ninth embodiment of the presentinvention;

[0296]FIG. 226 is a figure showing another embodiment of a protocolcontrol record and port control record, in the ninth embodiment of thepresent invention;

[0297]FIG. 227 is a figure showing still another embodiment of aprotocol control record and port control record, in the ninth embodimentof the present invention;

[0298]FIG. 228 is a figure showing a communication flow between an ASPsite and a terminal unit, in the ninth embodiment of the presentinvention;

[0299]FIG. 229 is a figure showing a packet to be communicated betweenan ASP site and a terminal unit, in the ninth embodiment of the presentinvention;

[0300]FIG. 230 is a figure explaining a method to communicate with anASP site by using a terminal-unit program as a server, in the ninthembodiment of the present invention;

[0301]FIG. 231 is a figure showing a packet to be communicated between aterminal-unit program and an ASP site, in the ninth embodiment of thepresent invention;

[0302]FIG. 232 is a figure showing a communication flow between aterminal-unit program and an ASP site, in the ninth embodiment of thepresent invention;

[0303]FIG. 233 is a figure showing LAN lease service and ASP-site jointutilization, in the ninth embodiment of the present invention;

[0304]FIG. 234 is a figure showing a communication flow concerning LANlease service and ASP-site joint utilization, in the ninth embodiment ofthe present invention;

[0305]FIG. 235 is a figure explaining a multicast data flow within IPnetwork, in a tenth embodiment of the present invention;

[0306]FIG. 236 is a figure showing a record of an address managementtable of within a network node unit, in the tenth embodiment of thepresent invention;

[0307]FIG. 237 is a figure showing a route table record of within arouter, in the tenth embodiment of the present invention;

[0308]FIG. 238 is a figure comparing between a communication record of aunit control table and a record of an address management table, in thetenth embodiment of the present invention;

[0309]FIG. 239 is a figure explaining a multicast data flow within an IPnetwork connected with media routers, in the tenth embodiment of thepresent invention;

[0310]FIG. 240 is a figure explaining a multicast data flow within an IPnetwork connected with media routers and radio base points, in the tenthembodiment of the present invention;

[0311]FIG. 241 is a figure showing an IP network including terminal endsection allowing multicast, in the tenth embodiment of the presentinvention;

[0312]FIG. 242 is a figure showing multicast receive request and endprocedures, in the tenth embodiment of the present invention;

[0313]FIG. 243 is a figure showing an external packet to be used in amulticast receive request procedure, in the tenth embodiment of thepresent invention;

[0314]FIG. 244 is a figure showing an internal packet to be used in amulticast receive request procedure, in the tenth embodiment of thepresent invention; and

[0315]FIG. 245 is a figure showing a change in the items within a recordof an address management table of within a network node unit 1101, inthe tenth embodiment of the present invention;

DESCRIPTION OF THE PREFERRRED EMBODIMENTS

[0316] The present invention realizes a novel terminal-to-terminalcommunication control system for IP full service by a combination of anIP encapsulation technique disclosed in the prior patent, a method ofdynamically setting an address management table, an IP addressacquisition method using a telephone number as a domain name, asimplified encapsulation method disclosed in the prior patentapplication, a method of applying to an IP network a common channelsignaling system disclosed in the prior patent application, and amulticast technique disclosed in the prior patent application.Furthermore, the foregoing problem is resolved by communicating lineconnection control messages, such as “IAM, ACM, CPG, ANM, REL, RLC” thata common channel signaling system is applied to an IP, between a mobilecommunication network and an IP network, or establishing a communicationpath for terminal-to-terminal communication by communicating lineconnection control messages applied to an IP network after establishinga TCP communication path between a source-sided telephone managementserver and a destination-sided telephone management server, or applyinga multicast function to TV conference, or applying a multicast functionto a terminal-to-terminal communication to connect between a mobilecommunication and an IP network, or setting an external address set inan external IP packet to an address area of an internal packet to forman internal packet.

[0317] Japanese Patent Application No. 128956/1999 discloses that anintegrated IP communication network is internally separated into aplurality of IP networks, i.e. an IP data network, an IP telephonenetwork, an IP voice image network, a best effort network and an IP datamulticast network so that the network node units can be connected to anyof the IP networks. Herein, the IP network separation into a pluralityis realized by utilizing a technique of connection to any of the IPnetworks correspondingly to a record of within a network node unitmanaging encapsulation and decapsulation, i.e. by utilizing a differencein the address registered in an address administration record managingencapsulation and decapsulation. However, in the case that there is nodifference in the addresses to be registered in the record, a method forseparating into a plurality of IP networks has not been disclosed.

[0318] 1. Embodiment 1 of Terminal-to-Terminal Communication ConnectionControl Using Mobile Communication and IP Networks:

[0319] In FIG. 17, numeral 100 is an IP network under the operation andmanagement of a communication company X, numeral 101 is a mobilecommunication network under operation and management of a communicationcompany Y, numeral 102 is a public switched telephone network (PTSN),numeral 103 is a terminal-unit gateway, numeral 104 is a terminal-unitcontrol section, numerals 105 and 105-1 are network node units, numeral106 is a relay gateway, numeral 107 is a relay control section, numeral108 is a voice control section and numeral 113 is a network node unit.The network node unit 113 encapsulates or decapsulates a voice IP packetin passage. Numerals 110 and 111 are routers, numerals 112 and 115 arecontrol communication lines, numerals 114 and 114-1 are voicecommunication lines, numeral 116 is a media router, numeral 117 is acommunication line, numerals 120 and 121 are toll switches, numeral 122is a terminal-unit exchange, numeral 123 is a service information node,numeral 124 is a signal end point (SEP), numeral 125 is a signaltransfer point (STP), numeral 126 is a speech path section of theexchange 122, numeral 127 is a speech path section of the toll switch120, numerals 128-1 to 128-3 are relay units, numerals 129-1 to 129-3are communication lines, numeral 130 is a radio base point in the mobilecommunication network 101. Numerals 131, 132 and 170 are controlcommunication lines on the common channel signaling system, numerals133, 134 and 171 are voice communication lines, and numeral 138 is aradio communication line. Numeral 140 is a telephone set for connectionto the telephone network 102. Numeral 141 is a telephone set, andnumeral 142 is a telephone set for connection to the media router 116 byway of the communication line 137. The set of the control communicationline 131 and the voice communication line 133 is an NNI (network-networkinterface) of an exchange network while the set of the controlcommunication line 132 and the voice communication line 134 is also anNNI. Numerals 120 to 123 are connected together by a communication linevia any of the relay units 128-1 to 128-3 and allowed to exchangeinformation with each other. The telephone set 141 has a function tocommunicate with a base point via a radio communication line, hence tobe considered as a mobile phone. The phone sets 140 and 142 to beconsidered as fixed phone set.

[0320] Between the IP network 100 and the public switched telephonenetwork 102, communication is possible via an NNI line formed by a setof a control communication line 170 and a voice communication line 171.The detailed procedure of communication is disclosed in the prior patentapplication (fourteenth embodiment, etc.).

[0321] <<Connection Phase>>

[0322] This is an example of telephone communication from the telephoneset 141 to the telephone set 142. In FIG. 18, numeral 100-1 represents arange of the IP network 100 while numeral 101-1 a range of a mobilecommunication network. Within the range 100-1, communicated are a seriesof line control messages (IAM, ACM, CPG, ANM, REL, RLC, etc.) stored inan IP packet conforming, at least, to the common channel signalingsystem. Within the range 101-1, communicated are a series of linecontrol messages (IAM, ACM, CPG, ANM, REL, RLC, etc.) defined, at least,by the common channel signaling system. When the telephone set 141forwards a connection request via the radio communication line 138, aradio channel connection request signal is conveyed to the radio basepoint 130 (Step E01). The radio base point 130 make an acceptanceconfirmation to the base point (Step E02).

[0323] Then, call-set request information including a telephone number“TN1” of a telephone 141 as an origin and a telephone number “TN2” of atelephone 142 as a destination is forwarded from the telephone set 141to a radio base point 130 (Step E03). The radio base point 130 sends acall-set request information to a signal end point 124 of within theterminal-unit exchange 122 via the communication line 135 (Step E04).The signal end point 124 receives the call-set request information andexamines a content of the call-set request information, to forward atransmission-information inquiry message including the receivedtelephone number “TN2” of the telephone set 142 to a service informationnode 123 (Step E05). The service information node 123, considering thetelephone number “TN2” as information for connection, answers asignaling point code “PC125” of the signal transfer point 125 to thesignal end point 124 (Step E06). Call-set acceptance information is sentfrom the signal end point 124 to the radio base point 130 (Step E07).The radio base point 130 sends a call-set acceptance information to thetelephone set 141 (Step E08).

[0324] Then, the terminal-unit authentication information formed byinformation unique to the telephone set 141 is sent from the telephoneset 141 to the signal end point 124 of within the terminal-unit exchange122 (Step Eli) via the radio base point 130 (Step E10). The signal endpoint 124 examines the received terminal-unit authenticationinformation, to notify speech-channel set information to a mobile radiounit via the radio base point 130 (Steps E12, E13). The signal end point124 forms an initial address message (IAM) defined by the common channelsignaling system, and forwards it onto a communication line 129-1.Thereupon, the initial address message reaches the signal transfer point125 by way of a communication line 129-1, a relay unit 128-1 andcommunication line 129-2 (Step E14). When the signal transfer point 125forwards the received initial address message onto a controlcommunication line 131 (Step E15), the initial address message definedby the common channel signaling system, in the relay control section107, is converted into an IAM packet 151 for transfer within the IPnetwork 100 (FIG. 17, FIG. 19). The IAM packet 151 is forwarded onto acommunication line 112 to reach the terminal-unit control section 104 ofwithin a terminal-unit gateway 103 by way of a router 110 andcommunication line 115 (Step E16).

[0325] The IAM packet 151 contains a source IP address “1107”, adestination IP address “1104”, a circuit identification code “CIC-1”, amessage “IAM” and a parameter. The parameter includes the telephonenumbers “TN1” and “TN2”. The source IP address “1107” is an IP addressprovided to the relay control section 107 while the destination IPaddress “1104” is an IP address provided to the terminal-unit controlsection 104. The IAM packet 151 contains an IP packet header 151-1 and,in its payload section, a UPD segment 151-2. The source port number inthe UPD header 151-3 is used to identify a telephone management serverof within the relay control section 107. The destination port number inthe UPD header 151-3 is used to identify a telephone management serverof within the terminal-unit control section 104.

[0326] The terminal-unit control section 104 forms an IP packetnotifying a call request and sends it to the media router 116 on thebasis of a received IP packet 151 for call connection control (StepE17). The media router 116 receives the IP packet. The media router 116notifies a call-set request to the telephone set 142 (Step E20). Themedia router 116 then sends an IP packet notifying a reception in theStep E17 back to the terminal-unit control section 104 (Step E21). Theterminal-unit control section 104 forms an ACM packet 152 (FIG. 17, FIG.20) containing an address completion message in its payload section ofan IP packet on the basis of the IP packet notifying the reception, andsends it back to the relay control section 107 (Step E22). The ACMpacket 152 is converted, in the relay control section 107, into an ACMmessage on the common channel signaling system to be handled in themobile communication network 101, and transferred over a control line131 to reach the relay control section 125 (Step E23), then reaching therelay control section 124 by way of a communication line 129-2, a relayunit 128-1 and a communication line 129-1 (Step E24). The ANM packet 152contains an IP packet header 152-1 and, in its payload section, a UDPsegment 152-2. The source port number in the UPD header 152-3 is used toidentify a telephone management server of within the terminal-unitcontrol section 104. The destination port number in the UPD header 152-3is used to identify a telephone management server of within the relaycontrol section 107.

[0327] When the telephone set 142 notifies an in-calling notification tothe media router 116 (Step E30), the notification is forwarded to theterminal-unit control section 104 via a media router 116 andcommunication line 117 (Step E31). The terminal-unit control section 104forms, in its payload section of an IP packet, a CPG packet 153 (FIG.21) containing a call progress message notifying an incoming callringing on the basis of the IP packet notifying an incoming callringing, and sends it back to the relay control section 107 (Step E32).In the relay control section 107, the CPG packet 153 is converted into aCPG message on the common channel signaling system to be handled in themobile communication network 101, to reach the relay control section 125via the control line 131 (Step E33). The CPG packet 153 contains an IPpacket header 153-1 and, in its payload section, a UDP segment 153-2.

[0328] Furthermore, reaching the relay control section 124 by way of acommunication line 129-2, a relay unit 128-1 and a communication line129-1 (Step E34), a signal notifying an incoming call ringing isnotified to the radio base point 130 (Step E35), while a ring back toneis notified onto the telephone set 141 (Step E36). The ANM packet 154contains an IP packet header 154-1 and, in its payload section, a UDPsegment 154-2.

[0329] When the telephone set 142 reply, a response notification reachesthe media router 116 and the terminal-unit control section 104 (StepE40, Step E41). The terminal-unit control section 104 forms an ANMpacket 154 (FIG. 22) containing, in a payload section of IP packet, ananswer message notifying an incoming call ringing on the basis of the IPpacket notifying response and sends it back to the relay control section107 (Step E42). In the relay control section 107, the ANM packet 154 isconverted into an ANM message on the common channel signaling system tobe handled in the mobile communication network 101. By way of the relaycontrol section 125, a relay router 128-1, a relay control section 124and a radio base point 130, a response is notified to the telephone set141, thus allowing for telephone communication (Steps E43 to E46).

[0330] A voice IP packet is communicated between the telephone set 141and the telephone set 142, to effect voice communication (Step E48). Thevoice sent from the telephone set 141 reaches the telephone set 142 byway of the radio communication line 138, the radio base point 130, thecommunication line 135, the speech path section 126, the communicationline 129-3, the relay units 128-2, 128-3, the speech path section 127,the voice communication line 133, the voice control section 108, thenetwork node unit 113, the router 111 and the communication line 114 andby way of the network node unit 105, the communication line 117 and themedia router 116. The voice forwarded from the telephone set 142 istransferred in a direction reverse to the above, to reach the telephoneset 141. It is disclosed in Embodiment 13 (FIG. 227, etc.) of the priorpatent application that, in the voice control section 108 and networknode unit 105, digitized voice data is IP-encapsulated or -decapsulatedfor an IP packet. Numeral 155 in FIG. 23 shows an example of an IPpacket storing digitized voice data.

[0331] When the telephone set 141 issues a release request (Step E50),carried out is a series of procedures for call release and releasecompletion of under telephone line connection control according to thecommon channel signaling system (Steps E51 to E56, Steps E60 to E66).Then, a radio channel disconnect signal is forwarded from the exchange122 and notified to the radio base point 130 (Step E70), thereby beingnotified to the telephone set 141 via the radio base point 130 (StepE71). The telephone set 141 sends a disconnection confirmation signalback to the radio base point 130, and the disconnect signal passes thetelephone set 141 (Step E72) to reach the exchange 122 (Step E73).

[0332] The series of Steps E01-E73 enables a telephone communication atbetween the telephone sets 141 and 142. Incidentally, in the Step E54,there has been formed and transferred an REL packet 156 (FIG. 24)containing a release message notifying a release of telephonecommunication (closure of voice communication) formed in a payloadsection of the IP packet. In Step E62, there has been formed andtransferred an RLC packet 157 (FIG. 25) containing a release completionmessage notifying a release completion of telephone communication(confirmation of a release) in a payload section of the IP packet. TheREL packet 156 contains an IP packet header 156-1 and, in its payloadsection, a UDP segment 156-2. The RLC packet 157 contains an IP packetheader 157-1 and, in its payload section, a UDP segment 157-2. Theinternal IP packet, to be communicated between the terminal-unit controlsection 104 and the relay control section 107, has a prototype in its IPpacket header designated “UPD”, to contain the line-connection controlmessages, as an NNI interface, in a UPD payload section set in theinternal IP packet payload section.

[0333] Incidentally, the communication step of between the radio basepoint 130 and the terminal-unit signal transfer point 124 (UNIinterface) can be changed in procedure to the other than the above, e.g.changing the Steps E07 and E11 to other steps or omitting them.

[0334] <<Explanation of Port Number>>

[0335] Explanation is made on “EA8”, “5006” and “Info-1” contained in aparameter area of the IAM packet 151 of FIG. 19. “EA8” is an IP addressprovided to a voice communication port within the voice control section108. “5006” is a port number within the UDP packet holding a digitalvoice to be transmitted from the voice control section 108. “Info-1” isattendant information, e.g. in a voice compression form, to be forwardedfrom the relay control section 107 toward the media router 116, having asignificance only for a call having a call identifier “CIC-1”.Explanation is made on “EA2”, “5008” and “Info-2” contained in aparameter area of the CPG packet 153 of FIG. 21. “EA2” is an IP addressprovided to a voice communication port within the terminal-unit controlsection 104. “5008” is a port number within the UDP packet holding adigital voice to be transmitted from the terminal-unit control section104. “Info-2” is attendant information to be forwarded from theterminal-unit control section 104 toward the relay control section 107,having a significance only for a call having a call identifier “CIC-1”.This is true for “EA2”, “5008” and “Info-3” contained in a parameterarea of the ANM packet 154 of FIG. 22, wherein “Info-3” is attendantinformation to be forwarded from the terminal-unit control section 104toward the relay control section 107.

[0336] Next, in the case of changing the network node unit 105 and voicecontrol section 108 into another network node unit and voice controlsection not having an IP encapsulation function, a digitalized voice isin a form of “158” in FIG. 26 wherein an IP header for IP encapsulationis not provided.

[0337] <<Transmission from IP-Network-Sided Telephone Set toMobile-Network-Sided Telephone Set>>

[0338] With reference to FIG. 27, explanation is made on a telephonecommunication of from a telephone set 142 for connection on a side ofthe IP network 100 to a telephone set 141 for connection on a side ofthe mobile communication network 101.

[0339] First, a connect request is forwarded from the telephone set 142(Step F01), and the media router confirms an acceptance (Step F02). Themedia router 116 sends, to the terminal-unit control section 104, thecall-set request information including a telephone number “TN2” of thetelephone set 142 as an origin and a telephone number “TN1” of thetelephone set 141 as a destination (Step F04). The terminal-unit controlsection 104, receiving the call-set request information, forms aninitial address message (IAM) for transfer within the IP network 100,and forwards it to the control communication line 115 (Step F05). Theinitial address message reaches the relay control section 107. The relaycontrol section 107 converts the initial address message (IAM) into aninitial address message in the form of the common channel signalingsystem and forwards it onto the control communication line 131 (StepF06). The signal transfer point 125 extracts a transmission-informationinquiry message including the telephone number “TN1” of the telephoneset 141 from the received initial address message (IAM), and forwards itto the service information node 123 (Step F07). Thereupon, the serviceinformation node 123 answers a point code “PC124” of signal end point124 as information to connect for the telephone number “TN1” (Step F08).The signal transfer point 125 sets again the point code “PC124” as adestination address of the received initial address message (IAM) andforwards it onto the communication line 129-2. Thereupon, the resetinitial address message reaches the signal end point 124 by way of thecommunication line 129-2, a relay unit 128-1, and a communication line129-1 (Step F10).

[0340] The signal end point 124 forwards a call-set request to the basepoint 130 on the basis of the received initial address message (IAM)(Step F11). The base point 130 notifies a call to the telephone set 141via the radio communication path 138 (Step F12). The telephone set 141reports a state of the radio communication path 138 (noise, voicequality, etc.) to the radio base point 130 (Step F13), and subsequentlynotifies the signal end point 124 of the information meaning aterminal-unit correctness, e.g. including password forwarding, by way ofthe radio base point 130 (Step F15, Step F16). The signal end point 124notifies a communication channel set instruction to the telephone set141 via the radio base point 130 (Step F17, Step F18). The signalendpoint 124 then notifies a call set request to the telephone set 141via the radio base point 130 (Step F20, Step F21), and forms an addresscompletion message (ACM) on the common channel signaling systemnotifying a reception permission of a call set request based on theinitial address message and sends it to the signal transfer point 125(Step F22). The address completion message (ACM) reaches the relaycontrol section 107 via the control line 131 (Step F23). The addresscompletion message (ACM) in the relay control section 107 is convertedinto an ACM packet in a form to be handled within the IP network, toreach the terminal-unit control section 104 via the router 110 (StepF24). The call set request information reaches the media router 116 viathe communication line 117 (Step F25).

[0341] By forwarding an in-calling by the telephone set 141, anin-calling notification passes the base point 130 (Step F30) and reachesthe signal end point 124 (Step F31). The signal endpoint 124 forms andforwards a call message (CPG) (Step F32). The call message (CPG) reachesthe signal transfer point 125, the control communication line 131 andthe relay control section 107 (Step F33, Step F34). The relay controlsection 107 notifies a ringing notification to the telephone set 142 viathe media router 116 (Step F35, Step F36).

[0342] When the telephone set 141 responds, a response notificationreaches the signal end point 124 via the base point 130 (Step F40). Thesignal end point 124 forwards a confirm notification to the telephoneset 141 via the radio base point 130 (Steps F42, Step F43). The signalend point 124 forms and forwards an answer message (ACM) (Step F44). Theanswer message (ACM) reaches the relay control section 107 by way of thesignal transfer point 125 and control communication line 131 (Steps F45,F46). The relay control section 107 notifies a response notification tothe telephone set 142 via the media router 116, thereby enabling voicecommunication (Steps F47, F48).

[0343] By the above procedure, the voice IP packet is communicatedbetween the telephone set 141 and the telephone set 142, thus effectingvoice communication (Step F50). When the telephone set 142 issues arelease request (Step F51), a procedure of call release and releasecompletion similarly to the foregoing (Steps F52 to F70) is made to endthe telephone communication. Herein, the Steps F54 to F56 are on arelease request message REL while the Steps F61 to F63 are on a releasecompletion message RLC.

[0344] Incidentally, the communication step of between the telephone set141 and the terminal-unit signal transfer point 124 can be changed tothe other procedure than the above, e.g. the Step F13 to Step F18 can bechanged to other steps or omitted. It is possible that other messages ofthe common channel signaling system are introduced to this embodiment,examples are SUS message for suspending temporarily circuit connectioncontrol, and RES message for restarting the suspending.

[0345] <<Setting and Releasing Address Management Table in Network NodeUnit>>

[0346] As in the foregoing, within the IP network, the external IPpacket is IP-encapsulated into an internal IP packet. Consequently, usedis a record of an address management table of within the network nodeunit. Accordingly, after establishing a series of call connectioncontrols mentioned in FIG. 27, i.e. after sending/receiving an ANNmessage, set is an address management table record in the network nodeunit. Also, after a series of call releases, i.e. aftersending/receiving an RLC message, erased is the address management tablein the network node unit. However, the record setting and release forencapsulation is disclosed in the prior patent or the patentapplication.

[0347] The IP network 100 employs a function of IP encapsulation anddecapsulation used in the prior patent. The function of the IP networkis to be summarized as in the following. The IP network 100 includes twoor more network node units. When inputting an external IP packet from alogical terminal unit at an end of the communication line 117, theexternal IP packet turns into an internal packet under the control ofthe address management table within the network node unit 105. Theinternal packet is transferred in the IP network to reach a network nodeunit 113. The internal packet is restored as an external IP packet underthe control of the address management table of within the network nodeunit 113.

[0348] <<Variation: Voice Image Communication through IP andMobile-Communication Networks>>

[0349] With reference to FIGS. 28 and 29, explanation is made on thevoice image communication from a voice image unit 152 connected at theside of the IP network 145 to a voice image unit 160 connected at theside of the mobile communication network 146. Incidentally, the voiceimage units 152 and 160 can be a terminal unit or telephone set having afunction to send/receive a voice and still image, a terminal unit ortelephone set having a function to send/receive a voice and movingimage, a cellular phone, or a TV broadcast transmitter or receiver.

[0350] A connection request is forwarded from the voice image unit 152(Step G01), and the media router 153 confirms an acceptance (Step G02).Then, the media router 153 sends, to the terminal-unit control section154, the call-set request information including a telephone number “TN2”of the voice image unit 152 as an origin and a telephone number “TN1” ofthe voice image unit 160 as a destination (Step G04). The terminal-unitcontrol section 154, receiving the call-set request information, formsan initial address message (IAM) and forwards it into the IP network 145(Step G05). The initial address message reaches the relay controlsection 155. The relay control section 155 converts the initial addressmessage into an initial address message (IAM) of the common channelsignaling system to be used in the mobile communication network 146 andforwards it onto the control communication line 164 (Step G06). Thesignal transfer point 156 extracts a transmission-information inquirymessage including the telephone number “TN1” of the voice image unit 160from the received initial address message (IAM), and forwards it to theservice information node 157 (Step G07). Thereupon, the serviceinformation node 157 answers a point code “PC158” of signal end point158 as information for connection for the telephone number TN1 (StepG08). The signal transfer point 156 sets the point code “PC158” again asa destination address of the received initial address message (IAM) andforwards it into the mobile network 146. Thereupon, the reset initialaddress message reaches the signal endpoint 158 (Step G11). The signalend point 158 forwards a call-set request to the base point 159 on thebasis of the received initial address message (Step G11). The base point159 notifies the voice image unit 160 of a communication call of fromthe voice image unit 152, via the radio communication path 163 (StepG12). The voice image unit 160 reports a state of the radiocommunication path 163 to the radio base point 159 (Step G13), andsubsequently notifies the signal end point 158 of the informationmeaning a terminal-unit correctness, e.g. including password forwarding,by way of the radio base point 159 (Step G15, Step G16). The signal endpoint 158 notifies a communication channel set instruction to the voiceimage unit 160 via the radio base point 159 (Step G17, Step G18). Thesignal end point 158 then notifies a call set request to the voice imageunit 160 via the radio base point 159 (Step G20, Step G21), and forms anaddress completion message (ACM) on the common channel signaling systemnotifying a reception permission of a call set request based on theinitial address message and sends it to the signal transfer point 156(Step G22). The address completion message (ACM) reaches the relaycontrol section 155 via the control line 164 (Step G23). The addresscompletion message (ACM) is converted into an ACM packet in a form to behandled within the IP network in the relay control section 155, andtransferred in the IP network 145 to reach the terminal-unit controlsection 154 (Step G24). The call set request information reaches themedia router 153 (Step G25).

[0351] By forwarding an in-calling by the voice image unit 160, anin-calling notification passes the base point 159 (Step G30) and reachesthe signal end point 158 (Step G31). The signal endpoint 158 forms andforwards a call message (CPG) (Step G32). The call message (CPG) reachesthe signal transfer point 156, the control communication line 164 andthe relay control section 155, 154 (Step G33, Step G34). The relaycontrol section 155 notifies a call notification to the voice image unit152 via the media router 153 (Step G35, Step G36).

[0352] When the voice image unit 160 responds, a response notificationreaches the signal end point 158 (Step G41) via the base point 159 (StepG40). The signal endpoint 158 forwards a confirm notification to thevoice image unit 160 via the radio base point 159 (Steps G42, Step G43).The signal end point 158 forms and forwards an answer message (ACM)(Step G44). The answer message (ACM) reaches the relay control section155, 154 by way of the signal transfer point 156 and controlcommunication line 164 (Step G45, Step G46). The relay control section155 notifies a response notification to the voice image unit 152 via themedia router 153, thereby enabling voice image communication (Steps G47,G48, G49).

[0353] By the above procedure, a communication path for connecting theIP network and the mobile communication network is established atbetween the voice image unit 152 and the voice image unit 160. Next, thevoice image unit 152 and the voice image unit 160 carry out a controlprocedure for voice image communication of opening a voice imagecommunication logic channel, communication mode selection, flow-controldesignation and terminal-unit capability information exchange (StepG50-1). The control procedure can adopt, for example, a multimediacommunication system H.245 control procedure under ITU-T recommendation.Next, an IP packet storing a multimedia data such as voice and image iscommunicated between the voice image unit 152 and the voice image unit160, thereby effecting voice image communication (Step G50-2). The IPpacket including multimedia data is transported through the voicecommunication line 165 of a mobile communication line. The voice imageunit 152 and the voice image unit 160, when ending the voice imagecommunication, execute a control procedure to close the opened voiceimage communication path (Step G50-3).

[0354] When the voice image unit 152 issues a release request (StepG51), a procedure of call release and release completion, as in theforegoing, is made (Steps G51 to G70) to release the communication pathconnecting between the IP communication network and the mobilecommunication network set up for voice image communication. At thistime, one of the voice image units 152 and 154 issues a release request,to communicate a release request message REL and release completionmessage RLC in the mobile communication and IP networks, thus releasingthe communication of between the two voice image units.

[0355] Incidentally, the communication step of between the voice imageunit 160 and the terminal-unit signal transfer point 158 can be changedto the other procedure than the above, e.g. the Step G13 to Step G18 canbe changed to another step or omitted. Also, although, in the above, aterminal-to-terminal connection request was issued from the voice imageunit 152 connecting to the IP network 145 to the voice image unit 160connecting to the mobile communication network 146, aterminal-to-terminal connection request can be issued in the reversedirection of from the voice image unit 160 to the voice image unit 152.This is disclosed by the similar example in the former half portion ofthis embodiment. The voice image unit can be provided with a functionfor sending and receiving a voice/moving image.

[0356] <<Summary>>

[0357] The mobile phone set 141 makes a telephone communication with thefixed phone set 142 by way of the radio communication path 138 and basepoint 130, and by way of terminal-unit exchange 122 in the mobilecommunication network, communication lines 129-1 to 129-2 in the mobilecommunication network, toll switch 120 in the mobile communicationnetwork, a combination of NNI communication lines 131 and 133 at betweenthe mobile communication network and the IP network, a relay gateway 106of the IP network, internal communication lines 112 and 115, 114 of theIP network, a terminal-unit gateway 103 of the IP network, a mediarouter 116 and a communication line 137. Consequently, in the mobilecommunication network 101, line connection control is carried out basedon the common channel signaling system. In the IP network, acommunication path is established by communicating line connectioncontrol messages applying the common channel signaling system to the IPnetwork, thus effecting telephone communication.

[0358] Meanwhile, the IP network includes two or more network nodeunits. An external IP packet is inputted at a logic terminal at an endof the communication line. The external IP packet turns into an internalpacket under the control of an address management table of within thesource-network node unit. The internal packet is transferred in the IPnetwork to reach a destination-sided network node unit. The internalpacket is restored as an external IP packet under the control of anaddress management table of within the destination-sided network nodeunit.

[0359] Meanwhile, the voice image unit 1 carries out a voice imagecommunication with the voice image unit 2 by way of the mobilecommunication network, NNI communication line and IP network.Consequently, in the mobile communication network, line connectioncontrol is effected on the common channel signaling system. In the IPnetwork, a communication path is established by communicating the lineconnection control applying the common channel signaling system to theIP network. Thereafter, a control procedure for opening a voice imagecommunication path (e.g. ITU-T or H.245 control procedure) is madebetween the two voice image units. An IP packet storing a voice andimage can be communicated between the voice image unit 152 and the voiceimage unit 160, to effect voice image communication. When the voiceimage communication ends, the voice image unit 152 and the voice imageunit 160 carry out a control procedure to close the opened voice imagecommunication path (media communication path). Next, when the voiceimage unit 152 or 154 issues a request for releasing the communicationpath due to a line connection control message, a release request messageREL and release completion message RLC is communicated within the mobilecommunication and IP networks, on the basis, for the mobilecommunication network, of a line connection control protocol based onthe common channel signaling system and, for the IP network, of a lineconnection control protocol applying the common channel signaling systemto the IP network, to thereby release the communication between the twovoice image units.

[0360] A communication path is opened using telephone numbers betweenthe voice image unit 1 and the voice image unit 2, to effect voice imagecommunication. Thereafter, the voice image communication path isreleased. The image may be any of a still image and a moving image. Inthis embodiment, the internal IP packet has a prototype designated UDPin a header, wherein the circuit connection control message (IAM, ACM,CPG, ANM, REL, RLC) is set with a UDP segment in a payload of the IPpacket (IPv4) defined under RFC 791. The other methods include a methodof defining “CC” representative of line connection control as a newprototype to store line connection control messages in the payload ofthe internal IP packet. Furthermore, another method is to designate aprotocol type as “ICMP” to store it in an ICMP message region to be setin a payload section of an internal IP packet. Also, a TCP segment canbe provided in place of the UDP segment, which is explained in anotherembodiment. It is possible to carry out as an IP packet (IPv6) definedunder RFC 1883.

[0361] 2. Embodiment 2 for Implementing Line Connection Control ProtocolUsing Telephone Numbers, in Level Above TCP Layer:

[0362] This embodiment is a method for carrying out a line connectioncontrol protocol in a level above a TCP layer, i.e. a method forcarrying out a line connection control protocol after setting up a TCPcommunication path. FIG. 30 shows a communication function layers. Thereare shown a physical layer (communication first layer), a data-linklayer (communication second layer), an IP layer (communication thirdlayer or network layer) and a TCP/UDP layer (communication fourth layeror transport layer), in the order of from the lower to the upper. A lineconnection control protocol conforming to the common channel signalingsystem is provided in a level above the communication first to fourthlayers. Furthermore, in the level above the line connection controlprotocol, SIP, H322 signaling protocol, H245 protocol or the like is setup as a communication protocol for terminal-to-terminal connectioncontrol described in the prior patent application or the like. The lineconnection control protocol conforming to the common channel signalingsystem refers to a call control message, such as IAM, ACM, CPG, ANM, RELor RLC, shown in Embodiment 1 in the prior patent application.

[0363] Explanation is made with reference to FIG. 33. Numeral 221-1 isan IP transfer network, numerals 222-2 and 222-3 are LANs, numerals223-1 and 223-2 are terminal-unit gateways, numerals 225 and 230 areterminal units, numerals 226 and 229 are media routers, and numerals 227and 228 are telephone management servers. Network node units 231 and 232include the function of IP-encapsulation and -decapsulation used in theprior patent. The IP network 222-1 includes two or more network nodeunits. An external IP packet is inputted at a logic terminal at an endof the communication line. The external IP packet turns into an internalpacket under the control of an address management table of within thesource-sided network node unit. The internal packet is transferred inthe IP network to reach a destination-sided network node unit. Theinternal packet is restored as an external IP packet under the controlof an address management table of within the destination-sided networknode unit.

[0364] The terminal units 225 and 230 (FIG. 33) are terminal unitshaving a function of digital media transmission/reception. Asource-sided telephone management server 227 sends a “SYN” packet to adestination-sided telephone management server 228. The telephonemanagement server 228 sends an “ACK” packet to the telephone managementserver 227. After establishing a TCP communication path within thetelephone management servers 227 and 228, call control messages of IAM,ACM, CPG, ANM, REL, RLC and the like are processed in the level abovethe TCP layer, on the basis of the line connection control protocol. Inthe first method, as shown in FIG. 31, a “SYN” packet for establishing aTCP communication path is sent from the telephone management server 227to the telephone management server 228 (Step 210-1 in FIG. 31), while a“ACK” packet is sent from the telephone management server 228 back tothe telephone management server 227 (Step 210-2). Next, a series of callcontrol messages IAM, ACM, CPG, ANM are communicated between thetelephone management server 227 and the telephone management server 228,in order for setting a communication path based on the line connectioncontrol protocol between the both (Steps 211-1 to 211-4). Next,multimedia data such as voice or data is communicated between theterminal unit 225 and the terminal unit 230 (Step 214). In the Step 214,a telephone communication is possible using an SIP procedure or H323procedure. Completing the communication of multimedia data, call controlmessages REL, RLC are communicated between the telephone managementserver 227 and the telephone management server 228, to release thecommunication path based on the line connection control protocol (Steps211-5, 211-6). Next, a FIN packet for releasing the TCP communicationpath is sent from the telephone management server 227 to the telephonemanagement server 228 (Step 210-3). The telephone management server 228sends back an ACK packet (Step 210-4), to release the TCP communicationpath set up between the telephone management server 227 and thetelephone management server 228.

[0365] Incidentally, by commencing to send a FIN packet from thetelephone management server 228 to the telephone management server 227,it is possible to release the TCP communication path at between thetelephone management server 227 and the telephone management server 228.

[0366] The second method includes, as shown in FIG. 32, transmission ofa “SYN” packet for establishing a TCP communication channel from thetelephone management server 227 to the telephone management server 228(Step 218-1 in FIG. 32). An “ACK” packet is sent back from the telephonemanagement server 228 to the telephone management server 227 (Step218-2), to communicate a series of call-control messages of IAM, ACM,CPG and ANM for establishing a communication path based on a lineconnection control protocol at between the telephone management server227 and the telephone management server 228 (Steps 219-1 to 219-4, i.e.Step 220-1). Then, a FIN packet for TCP communication path release issent from the sender 227 to the recipient 228 (Step 218-3). Therecipient 228 sends back an ACK packet (Step 218-4). Then, an operationis entered to communicate voice or data between the terminal unit 225and the terminal unit 230 (Step 221). In the Step 214, a telephonecommunication is possible using an SIP procedure or H323 procedure. Whenmultimedia data communication is ended, a “SYN” packet for TCPcommunication path establishment is sent from the telephone managementserver 227 to the telephone management server 228 (Step 218-5 in FIG.32). An “ACK” packet is sent from the telephone management server 228back to the telephone management server 227 (Step 218-6). Then, callcontrol messages REL and RLC for releasing the communication path basedon the line connection control protocol are communicated between thetelephone management server 227 and the telephone management server 228(Steps 219-5, 219-6). A FIN packet is sent from the telephone managementserver 227 to the telephone management server 228 (Step 218-7). Thetelephone management server 227 sends back an ACK packet (Step 218-8),to release the TCP communication path set up between the telephonemanagement server 227 and the telephone management server 228.

[0367] <<Summary-1>>

[0368] A TCP communication path is previously established between asource-sided telephone management server and a destination-sidedtelephone management server. After establishing media communication pathby means of communicating line connection control messages IAM, ACM,CPG, ANM data and the like are communicated between the two terminalunits. Line connection control messages REL and RLC are communicatedbetween the source-sided telephone management server and thedestination-sided telephone management server to release the mediacommunication path, thus releasing the TCP communication path.

[0369] Another method includes establishing a TCP communication pathbetween a source-sided telephone management server and adestination-sided telephone management server, to thereafter establish amedia communication path communicating line connection control messagesIAM, ACM, CPG and ANM, and release the TCP communication path. Betweenthe two terminal units, multimedia data and the like are communicated.When one of the terminal units ends the communication of multimediadata, a new TCP communication path is established between thesource-sided telephone management server and the destination-sidedtelephone management server. Thereafter, line connection controlmessages REL and RLC are communicated to release the media communicationpath for terminal-to-terminal communicating, thereby releasing the newTCP communication path.

[0370] Detail explanation is made on another method for communicatingcall control messages IAM, ACM, CPG, ANM, REL and RLC forterminal-to-terminal communicating connection control after setting up aTCP communication path, with reference to FIG. 34. When a connectionrequest is sent from the terminal unit 225 to the media router 226 (Step240), the media router 226 makes sending back (Step 241). The mediarouter 225 when sending a connection request, an IP packet containing atransmission request reaches the telephone management server 227 via thenetwork node unit 231 (Step 242). Herein, the IP packet contains atelephone number of a calling terminal unit 225 and a called terminalunit 230.

[0371] The telephone management server 227 forms a SYN packet in orderto establish a TCP communication path and sends it to the telephonemanagement server 228 via the control line 235 (Step 243). The telephonemanagement server 228 sends back an ACK packet (Step 244). The telephonemanagement server 228 forms an initial address message IAM in a waysimilar to the disclosure in a tenth embodiment (FIG. 164, etc.) of theprior patent application, and sends the initial address message IAM tothe telephone management server 228 (Step 245). The telephone managementserver 228, receiving the initial address message IAM, sends anotification of call to the media router 229 (Step 246). The mediarouter 229 sends a notification of incoming call to the terminal unit230 (Step 247) and sends back an availability of the terminal unit 230to the telephone management server 228 (Step 248). The telephonemanagement server 228 forms an address completion message ACM in a waysimilar to the disclosure in the prior patent, and sends the addresscompletion message ACM to the telephone management server 227 (Step249). The telephone management server 227 sends an availability of theterminal unit 230 to the media router 226 (Step 250). The terminal unit230, upon knowing a connection request by the Step 247, sends back aconfirmation of request (Step 251). The terminal unit 230, furthermore,causes a ring-back tone and sends back a call start to the media router229 (Step 252). The media router 229 notifies a call notification to thetelephone management server 228 (Step 253). The telephone managementserver 228 forms a call progress message CPG in a way similar to thedisclosure in the prior patent, and sends the call progress message CPGto the telephone management server 227 (Step 254). The telephonemanagement server 227 notifies the media router 226 of an in-calling(Step 255). The media router 226 notifies the terminal unit of anin-calling (Step 256). The terminal 230, upon knowing a response by aterminal user, sends a notification of answer to the media router 229(Step 257). The media router 229 sends the answer back to the terminalunit 230 (Step 258) and notifies it to the telephone management server228 (Step 259). The telephone management server 228 forms an answermessage ANM in a way similar to the disclosure in the prior patent, andsends the answer message ANM to the telephone management server 227(Step 260). The telephone management server 227 notifies the mediarouter 226 of an answer from the terminal unit 230 (Step 261). The mediarouter 226 notifies the terminal unit 225 of the answer from theterminal unit 230 (Step 262). The terminal unit 225 sends a confirmationof answer back to the media router 226 (Step 263).

[0372] Through the above procedure, a communication path is establishedbetween the terminal unit 225 and the terminal unit 230. Between theboth terminal units, communication is possible with digitalizedmultimedia data such as voice, text data, video data and the like (Step264). Next, the terminal 225 issues a request for disconnecting acommunication path of between the terminal unit 225 and the terminal 230(Step 265). The media router 226 responds (Step 266), and the terminalunit confirms an answer (Step 267). Furthermore, the media router 226notifies the telephone management server 227 of a request fordisconnecting the communication path (Step 268). The telephonemanagement server 227 replies (Step 269). The telephone managementserver 227 forms a release message REL in a way similar to thedisclosure in the prior patent application, and sends the releasemessage REL to the telephone management server 228 (Step 270). Thetelephone management server 228 sends back a release completion messageRLC (Step 271). Then, the telephone management server 228 notifies themedia router 229 of a notification of releasing the communication path(Step 272). The media router 229 replies (Step 274) and further notifiesthe terminal unit 230 of a call disconnection (Step 273). The terminalunit 230 sends back a confirmation of release (Step 275). The mediarouter 229 sends a release completion to the terminal unit 230 (Step276). The telephone management server 227, upon receiving a releasecompletion message RLC by the Step 271, sends a FIN packet to thetelephone management server 228 in order to release the TCPcommunication path established between the telephone management server227 and the telephone management server 228 established in the Step 244(Step 277). The telephone management server 228 sends an ACK packet backto the telephone management server 227 in order for confirmation (Step278). The above releases the communication path between the terminalunit 225 and the terminal unit 230. It is possible that other messagesof the common channel signaling system are introduced to thisembodiment, examples are SUS message for suspending temporarily circuitconnection control, and RES message for restarting the suspending.

[0373] The above initial address message IAM, address completion messageACM, call progress message CPG, answer message ANM, release message RELand release completion message RLC are stored in a form of a TCP packet280 (see FIG. 35), respectively. In an extension of TCP header, can beinserted message segmentation “MSG” of the initial address message IAM,address completion message ACM, call progress message CPG, answermessage ANM, release message REL and release completion message RLCdisclosed in the prior patent application. However, the messagesegmentation “MSG” may be inserted in the TCP payload section.

[0374] Note that, in the procedure, it is possible to omit any of theSteps 250, 269 and 274 involved by the telephone management server 227or 228. Furthermore, in the procedure, it is possible to omit any of thesteps 241, 251, 258, 263, 266, 267, 275 and 276 involved by thetelephone set 225 or 230.

[0375] <<Kind of Terminal Unit>>

[0376] In the above embodiment, in the case that the terminal unit 225and the terminal unit 230 are telephone sets, a telephone communicationis allowed by using a terminal-to-terminal communication path to beestablished by the foregoing method. Meanwhile, where the terminal unit225 is a TV transmitter and the terminal unit 230 is a TV receiver,voice image communication using TV communication function is allowed byusing a terminal-to-terminal communication path to be established by theforegoing method. Where the terminal units 225 and 230 are computershaving data communication function, data communication through computercommunication is allowed by using a terminal-to-terminal path to beestablished by the foregoing method.

[0377] <<Summary-2>>

[0378] This embodiment is the method for implementing a line connectioncontrol protocol in a level above a TCP layer (method for implementing aline connection control protocol after setting up a TCP communicationpath). The IP network includes two or more telephone management servers.The media router outside IP network is connected with a terminal unithaving a function to transmit and receive digital media. An IP packet,for call setting, containing a calling telephone number and calledtelephone number is sent from the media router. The source-sidedtelephone management server forms a SYN packet to establish a TCPcommunication path and sends it to the destination-sided telephonemanagement server via a control line. The destination-sided telephonemanagement server sends back an ACK package responding withconfirmation. The calling telephone management server forms an initialaddress message containing call setting and sends a formed initialaddress message to the called telephone management server. The calledtelephone management server sends a call setting to the called mediarouter. Meanwhile, the called media router sends the call setting to thecalled terminal unit. The called telephone management server forms anaddress completion message and sends it to the calling telephonemanagement server. The called telephone management server, uponreceiving a report on an in-calling from the called terminal unit, formsa call progress message. The call progress message reaches the callingtelephone management server. The calling telephone management serversends an in-calling report of the called terminal unit to thesource-sided media router. The called telephone management server, uponreceiving a response from the called terminal unit, forms an answermessage. The answer message reaches the calling telephone managementserver. The calling telephone management server stops a ring-back toneon the called terminal unit. Thus, the calling terminal unit and thecalled terminal unit are allowed for terminal-to-terminal communicationto send and receive digital media by way of the calling and called mediarouters. Then, a terminal-to-terminal communication disconnect requestis sent from the calling or called media router to the telephonemanagement server. A release is sent from the telephone managementserver to the telephone management server at the other end. A disconnectinstruction is sent from the other-end telephone management server tothe other-end media router. A release completion is notified from theother-end telephone management server to the telephone managementserver. A disconnection completion is sent to the media router. In orderto release the TCP communication path established between thesource-sided telephone management server and the destination-sidedtelephone management server, a FIN packet is sent to thedestination-sided telephone management server. The destination-sidedtelephone management server sends an ACK packet to the source-sidedtelephone management server in order for conformation. In this manner,the connection and release of communication are carried out between thetwo terminal units.

[0379] 3. Embodiment 3 for TV Conference Communication Using IP-NetworkMulticast Function

[0380] In FIG. 36, numeral 300 is an IP network, numerals 311 to 315 arenetwork node units, numerals 317 to 319 are routers, and numerals 320 to327 are terminal units having a function to send and receive IP packets.The network node units and the routers are connected directly bycommunication lines or indirectly through the routers. The terminal unitis connected to any of the network node units via a communication line.The terminal unit is given with an IP address. The network node unitsare to be set with an address management table on the same principle asthat described, e.g. in FIGS. 293 to 295 of Embodiment 17 for multicastcommunication in the prior patent application. Namely, a multicast IPpacket can be encapsulated to form an internal packet, and the internalpacket can be decapsulated to restore a multicast IP packet.

[0381] The IP network 300 in its function is summarized, as follows. TheIP network 300 includes two or more network node units. An external IPpacket is inputted at a logic terminal at an end of a communicationline. The external IP packet turns into an internal packet under thecontrol of an address management table of within the source-sidednetwork node unit. The internal packet is transferred in the IP networkto reach a destination-sided network node unit. The internal packet isrestored as an external IP packet under the control of an addressmanagement table of within the destination-sided network node unit.

[0382] The terminal units 320 to 327 are further provided with thefunction to send and receive voice and moving images so that the voiceand moving images for TV conference can be sent and received bycommunicating IP packets between the terminal units. In this embodiment,the terminal unit 320, the terminal unit 322, the terminal unit 323, theterminal unit 325 and the terminal unit 327 operate to realize a TVconference transmitting and receiving the voice and moving images. Inparticular, the terminal unit 320, the terminal unit 323 and theterminal unit 327 serve as recipients and origins of voice and movingimages at the same time.

[0383] Explaining with reference to FIGS. 37 and 40 to 42, in order tomake the terminal unit 320 as an origin, a multicast internal addressIM1 is set in the network node units 311 to 315 and routers 317 to 319.When an IP packet 340 having an external destination address M1 is sentfrom the terminal unit 320, the IP packet 340 reaches the network nodeunit 311 and is transferred to the routers 317 and 319 according to anaddress management table 331 of within the network node unit 311. The IPpacket 341-1, reaching the router 317, is transferred to the networknode unit 312 and router 318 by the use of a route table 337. The IPpacket transferred to the network node unit 312 is transferred to theterminal unit 322 by the use of an address management table 332. The IPpacket 341-3, reaching the router 318, is transferred to the networknode units 313 and 314. The IP packet 341-4, reaching the network nodeunit 313, is decapsulated by the use of an address management table 333,and a restored IP packet 342-1 reaches the terminal unit 323. Meanwhile,the IP packet 341-5 reaching the network node unit 314 is decapsulatedby the use of an address management table 334, and a restored IP packet342-2 reaches the terminal unit 325. On the other hand, the IP packet343-2, forwarded from the network node unit 311 and reached the router319, turns into an IP packet 341-6 by the use of a route table 339. Thisis transferred over the communication line 344-3 to passes the networknode unit 315, and applied by an address management table 335. Arestored IP packet 342-3 reaches the terminal unit 327.

[0384] Next explaining with reference to FIG. 38, in order to make theterminal unit 323 as an origin, a multicast internal address IM2 is setin the network node units 311 to 315 and routers 317 to 319. When an IPpacket having an external destination address M2 is sent from theterminal unit 323, the IP packet reaches the network node unit 313,where the address management table 333 (see FIG. 42) of the network nodeunit 313 is used to form an internal packet. The internal packet istransferred to the router 318. Next, a route table (see FIG. 41) is usedin the router 318 so that the internal packet reaches the terminal unit325 via the network node unit 314. The other one IP packet reaches theterminal unit 327 by way of the router 319 and network node unit 315.The still other one IP packet is copied at the router 319, one of whichreaches the terminal 320 via the network node unit 311 and the otherreaches the terminal unit 322 via the network node unit 312.

[0385] Explaining furthermore with reference to FIG. 39, in order tomake the terminal unit 327 as an origin, a multicast internal addressIM3 is set in the network node units 311 to 315 and routers 317 to 319.When an IP packet having an external destination address M3 is sent fromthe terminal unit 327, the IP packet reaches the network node unit 315.This reaches the terminal unit 320, the terminal unit 322, the terminalunit 323 and the terminal unit 325 by way of the routers and networknode units similarly to the above. Note that the terminal units 322 and325 are examples that receive voice and moving image data but do nottransmit them.

[0386] <<Switching of Transmittal Right>>

[0387] The terminal unit 320 is allowed for information exchange withthe terminal unit 322, the terminal unit 323, the terminal unit 325 andthe terminal unit 327 by sending and receiving IP packets. The operationwill be explained in the below.

[0388] There are settings of a record “I01, E01, E07, I07, . . . ” online 4 from the top of the address management table 331 (see FIG. 40) inthe network node unit 311 and a record “I07, E07, E01, I01, . . . ” online 4 from the top of the address management table 332 in the networknode unit 312. Consequently, the terminal unit 320 having an IP addressE01 and the terminal unit 322 having an IP address E07 are allowed tosend and receive an IP packet. Similarly, there are settings of a record“I01, E01, E20, I20, . . . ” on line 5 from the top of the addressmanagement table 331 and a record “I20, E20, E01, I01, . . . ” in theaddress management table 333. Accordingly, the terminal units 320 and323 can send and receive an IP packet.

[0389] Similarly, there are settings of a record “I01, E01, E25, I25, .. . ” on line 6 from the top of the address management table 331 and arecord “I25, E25, E01, I01, . . . ” in the address management table 334.Consequently, the terminal units 320 and 325 can send and receive an IPpacket. Similarly, there are settings of a record “I01, E01, E28, I28, .. . ” on line 7 from the top of the address management table 331 and arecord “I28, E28, E01, I01, . . . ” in the address management table 335.Accordingly, the terminal units 320 and 328 can send and receive an IPpacket. With the above configuration, the terminal unit 320 cancommunicate IP packets and exchange information with the terminal unit323 or terminal unit 327, making it possible to switch, for example, asending terminal unit from the terminal unit 320 to the terminal unit327. Also, the terminal units 322 and 325 can exchange information withthe terminal unit 320.

[0390] <<Summary>>

[0391] In the network node unit within the IP network, set is an addressmanagement table for encapsulating and encapsulating a multicast IPpacket. In the router within the IP network, set is a route table usedfor transferring a multicast IP packet. A sender 1, within the IPnetwork, uses a multicast address M1 to transmit a multimedia data(voice and moving data) for TV conference communication, whilerecipients in plurality, within the IP network, use the multicastaddress M1 to receive the multimedia data. Meanwhile, a sender 2, in theIP network, uses a multicast address M2 to transmit a multimedia data,while recipients in plurality, in the IP network, use the multicastaddress M2 to receive the multimedia data. By the address managementtable in the network node unit, the IP packet is encapsulated andtransferred within the IP network to be decapsulated in a terminal-unitnetwork node unit, thus effecting communication for TV conference usingan IP packet. The terminal unit 320 exchanges the IP packet with otherterminal units, whereby it can exchange information for switching oftransmittal right, etc. Three or more persons can attend the TVconference.

[0392] 4. Embodiment 4 Showing a Configuration Method of Relay GatewayConnecting between IP Network and PSTN:

[0393] This embodiment shows a detailed example of a relay gateway 106(see FIG. 17) of Embodiment 1. This corresponds to a detail of the relaygateway (FIG. 197, etc.) in Embodiment 13 of the prior patentapplication. Explanation will be made with reference to FIG. 43.

[0394] Numeral 400 is a relay gateway, numeral 401 is a relay controlsection, numeral 402 is a voice control section, numeral 403 is aninformation line, numeral 404 is a control communication line on thecommon channel signaling system on a PSTN side, numeral 405 is a controlIP communication line, numeral 406 is a voice communication line on thePSTN side, numeral 407 is a voice IP communication line, numeral 408 isan address connection table, numeral 409 is a gateway address managementtable, numeral 410 is a signaling point address management table andnumeral 411 is a media path connection table. The relay gateway 400corresponds to the relay gateway 106 shown in FIG. 17 on Embodiment 1,while the relay control section 401 to the relay control section 107,and the voice control section 402 to the voice control section 108. Therelay gateway, relay control section, the voice control section, theinformation line, the PSTN-sided control communication line, the controlIP communication line, the PSTN-sided voice communication line, thevoice IP communication line, the address connection table, the gatewayaddress management table, the signaling point address management tableand the media path connection table shown at 400 to 411 are disclosed inEmbodiments 13 and 14 of the prior patent application.

[0395] Numeral 415 (FIG. 43) is a gateway MIB control section, numeral416 is a line connection control section, numeral 417 is a circuitidentification code management table, numeral 418 is a control IPcommunication line interface, numeral 419 is a PSTN control lineinterface, numeral 420 is a voice-call control section, numeral 421 is aspeech talk path section, numeral 422 is a media path control section,numeral 423 is a voice information control section, numeral 424 is anMIB control section, numerals 425 to 426 are channel state informationsections, numeral 428 is a channel MIB control section, numeral 429 is achannel information management, numeral 430 is a voice IP communicationline interface, numeral 431 is a converter section and numeral 432 is aPSTN voice communication line interface.

[0396] The elements of the relay gateway 106 (FIG. 17) of Embodiment 1can be placed in correspondence to the elements of the relay gateway 400(FIG. 43) of this embodiment, as follows. Namely, the relay controlsection 107 corresponds to the relay control section 401, the voicecontrol section 108 is to the voice control section 402, the controlcommunication line 112 in the IP transfer network 100 is to the controlIP communication line 405, the voice communication line 114-1 in the IPtransfer network 100 is to the voice IP communication line 407, thecontrol communication line 131 on the common channel signaling system onthe mobile communication network 101 is to the control communicationline 404 on the common channel signaling system on the PSTN side, andthe voice communication line 133 on a side of the mobile communicationnetwork 101 is to the voice communication line 406 on the common channelsignaling system on the PSTN side. Herein, it is known that there is nosubstantial difference between the NNI on a common channel signalingsystem in the mobile communication network and the NNI on the commonchannel signaling system in the PSTN. Similarly, the gateway 155 (FIG.28) can be placed in correspondence to the relay gateway 400 (FIG. 43)of this embodiment.

[0397] The gateway MIB control section 415 manages the operation statusof the gateway overall. The line connection control section 416 manageswhether call control is in normal operation. The circuit identificationcode management table 417 holds a circuit identification code for eachcall within the IP network. The control IP communication line interface418 manages IP packet transmission and reception. The PSTN control lineinterface 419 manages signal unit transmission and reception to and fromthe PSTN. The voice-call control section 420 (FIG. 43) managesvoice-call transfer paths and speech channel resources. The voice speechpath 421 is a voice speech section. The media path control section 422manages a media path connection table. The call information controlsection 423 records call information. The MIB control section 424manages the operation status of the voice-call control section. Thechannel-state information sections 425 to 426 manage on the use and inoccupation status of a voice channel within the voice PSTN communicationline 406. Meanwhile, the channel MIB control section 428 grasps a voicechannel resource state within the PSTN voice communication line 406. Thechannel information control 429 monitors a channel state within thevoice speech path block. The voice IP communication line interface 430transmits and receives the IP packets. The converter section 431performs conversion between the digital voice in an IP packet and thevoice block transferred in the PSTN communication circuit (codeconversion or frame form conversion) and fluctuation control. The voicePSTN communication line interface 432 transmits and receives a voiceframe transferred on the PSTN line.

[0398] <<Variation>>

[0399] With reference to FIG. 44, explanation is made on anotherembodiment of the relay gateway. Numeral 450 is a relay gateway, numeral451 is a relay control section, numerals 452 to 454 are a voice controlsections, numeral 455 is an information line, numeral 456 is a controlcommunication line on the common channel signaling system on the PSTNside, numeral 457 is a control IP communication line, numerals 458 to460 are voice communication lines on the PSTN side, numerals 461 to 463are voice IP communication lines.

[0400] The elements of the relay gateway 106 (FIG. 17) of the firstembodiment can be placed in correspondence to the elements of the relaygateway 450 (FIG. 44), as follows. Namely, the relay control section 107corresponds to the relay control section 451, the voice control section108 is to the voice control sections 452 to 454, the controlcommunication line 112 is to the control IP communication line 457, thevoice communication line 114-1 is to the voice IP communication lines461 to 463, the control communication line 131 is to the controlcommunication line 456 at PSTN side, and the voice communication line133 is to the voice communication lines 458 to 460 at PSTN side.

[0401] The relay control section 451 includes the same function as therelay control section 401 of FIG. 43, and can exchange information withany of the voice control sections 452 to 454 via the information line455. The voice control sections 452 to 454, in any, have the samefunction as the voice control section 402 of FIG. 43, and can be mountedon a plurality of physically separated boards. The information line 455is configured, for example, by an Ethernet branch line, and realizedunder conflict control on a CSMA/CD scheme. The voice communicationlines 458 to 460 can use, for example, an ISDN logic communication line(“B+23D” or the like). The voice IP communication lines 461 to 463 canbe connected to input/output circuit terminals of different routers.

[0402] <<Summary>>

[0403] This is an embodiment of the relay gateway of the firstembodiment (106 in FIG. 17) or the like. The relay gateway 400 (FIG. 43)includes a communication line having an NNI interface of a PSTN ormobile communication network based on the common channel signalingsystem, a communication line having an NNI interface based on the commonchannel signaling system within the IP network, a relay control sectionand a voice control section, and used to implement aterminal-to-terminal communication connection control method using an IPnetwork disclosed in the first embodiment. The relay gateway 450 (FIG.44) has voice control sections to be mounted separately on a pluralityof boards 452, 453, 454. The communication line having an NNI interfacecan be divided with a communication line having a control line interfaceand a voice communication line.

[0404] 5. Embodiment 5 for Setting Entire or Part of External Addressesin Internal Packet Address Area:

[0405] Explanation will be made on a terminal-to-terminal communicationconnection control method of forming an internal packet by setting anentire or part of the external addresses in address area of an internalpacket.

[0406] In FIG. 45, Numeral 500 is an IP network, numerals 501 to 504 arenetwork node units, numerals 505 to 508 are routers, numerals 509 and510 are LANs, and numerals 511 and 512 are terminal units within theLAN. The terminal unit 511 is given with an IP address EA1 while theterminal unit 512 is with an IP address EA2. The network node units andthe routers are connected directly by communication lines or indirectlyby way of the routers. The logic terminal 514 at a connection pointbetween the logic communication line 513 and the network node unit 501is given with an internal address P, while the logic terminal 516 at aconnection point between the logic communication line 515 and thenetwork node unit 502 is given with an internal address Q. When an IPpacket 520 having a source address EA1 and destination address EA2,transmitted from the terminal unit 511, reaches the network node unit501, it turns into an internal packet 523 by the use of an internalrecord of an address management table 521 on a method hereinafterreferred. The internal packet 523 is forwarded from the network nodeunit 501 to reach the network node unit 502 by way of the communicationline and routers 505, 506, 507. From the internal packet 523 reachingthe network node unit 502, an external packet 524 is restored. Theexternal packet 524 reaches the terminal unit 512 having an IP addressEA2 via the logic communication line 515. The external packet 524 hasthe same content as the external packet 520.

[0407] Next, explanation is made on a method to form an internal packetfrom an external packet to restore an external packet from the internalpacket. This embodiment explains that the external packet is an IPpacket defined under RFC791 (IPv4: packet having an address length of 32bits) and the internal packet is an IP packet defined under RFC1332(IPv6: packet having an address length of 128 bits). However, theinvention shown in this embodiment is unchanged in its substance ifthere is difference in packet type or address length. For example, theinvention can be carried out by adopting IPv6 as an external IP packet.The external IP packet 520 (FIG. 45) examines as to whether there existsa record of the internal address P given in the input logic terminal 514as an internal record of the address management table 521. In thepresent case, there exist a record on the first line and record on thesecond line in the address management table 521. Then, AND-operation(logical product) is made on the destination IP address EA2 of the inputexternal IP packet 520 and the destination IP address mask MK2 on thefirst-lined record. It is examined whether the result agrees with adestination address EA2x described in the first-lined record, accordingto the below Equation (1).

IF (“EA2” AND “MK2”=“EA2x”)  (1)

[0408] Similarly, inspection is made on the second-lined recordaccording to the below Equation (2).

IF (“EA2” AND “MK3”=“EA3y”)  (2)

[0409] In the present case, the above Equation (1) is held.

[0410] Next, AND-operation is made on the source IP address EA1 of theinput external IP packet 520 and the source IP address mask MK1x on thefirst-lined record. It is examined whether the result agrees with adestination address EA1x existing in the first-lined record, accordingto the below Equation (3).

IF (“EA1” AND “MK1x”=“EA1x”)  (3)

[0411] In the present case, the above Equation (3) is held.

[0412] From the fact that the Equations (1) and (3) are held on thefirst-lined record, selected is a destination internal address Qdescribed in the first-lined record. In this manner, fixed are theinternal addresses P and Q for forming an internal packet. Incidentally,where comparing between external addresses EA2 and EA1 in their parts,it is satisfactory to provide bit “1” in a range to be compared of themasks MK2 and MK1x and bit “0” in the range excluded from thecomparison. As hereinafter referred, when setting an external address ina part domain of an internal address, an internal address area forsetting an external address can be previously omitted from the record ofthe address management table 521.

[0413] In FIG. 46, a sign “X” represents an address area 526 having alength of 32 bits, while a sign “P” represents an address area 527having a length of 128 bits. FIG. 47 represents that an external IPpacket 530 is stored in a payload section 533 of an internal packet 531and further a source address X and destination address Y of an externalIP packet 530 is stored in a header extension 536 of the internal packet531. The header 535 stores an internal source address P (537) and aninternal destination address Q (538). In FIG. 48, a payload 546 of anexternal IP packet 540 is stored in a part 548 of a payload 543 of aninternal packet 541, the external IP packet 540 excluding a sourceaddress X and destination address Y from its header 544 is stored in apart 547 of the payload 543 of the internal packet 541. Furthermore, thesource address X and destination address Y of the external IP packet 540is stored in a header extension 545 of the internal packet 541. A header549 stores an internal source address P and internal destination addressQ.

[0414] In FIG. 49, an external IP packet 550 is stored in a payload 553of an internal packet 551, wherein an internal source address P (555)and internal destination address Q (556) is stored in a header 552 ofthe internal packet 551. This represent that a source address X of theexternal IP packet 550 is stored in an internal source address P (555)and a destination address Y of the external IP packet 550 is stored inan internal destination address Q (556). In FIG. 50, the sign “X”represents an address area 560 having a length of 32 bits while the sign“P” represents an address area 561 having a length of 128 bits. Theaddress area 560 is divided into two parts “a” and “b”, to representthat one part a is stored in a part domain a (562) of the address area561 while the other part b is stored in a part domain b (563) of theaddress area 561. Incidentally, the address area 560 may be divided intothree or more, to store them within the address area 561 by a waysimilar to the above. FIG. 51 represents that a part x of an addressarea 565 is stored within an address area 566.

[0415]FIG. 52 represents that an external IP packet 570 is stored in apayload 573 of an internal packet 571 and a part x of source address Xand part y of destination address Y of the external packet 570 is storedin a header extension domain 575 of the internal packet 571. Within aheader 572 are stored internal source address P (576) and an internaldestination address Q (577).

[0416] In FIG. 53, an external IP packet 580 is stored in a payload 583of an internal packet 581, and a source address P and internaldestination address Q is stored in a header 582 of the internal packet581. This represents that a part x of a source address X of the externalIP packet 580 is stored in an internal source address P (584) and a party of a destination address Y of the external IP packet 580 is stored inan internal source address Q (585).

[0417] The record in the address management tables 521 and 522 can beset in plurality. By changing the external destination address of theexternal IP packet, the destination of transfer can be changed for theinternal packet.

[0418] <<Summary>>

[0419] The IP network includes two or more network node units. Anexternal IP packet is converted into an internal packet in aninputted-sided network node unit and transferred within the IP networkand an external IP packet is restored from the internal packet in anoutput-sided network node unit. Under the control of the record in anaddress management table of within the input-sided network node unit,the entire or a part of an external address being set in the external IPpacket is set in an address area of the internal packet. The record inthe address management table can be set in plurality. By changing anexternal destination address of the external IP packet, the destinationof transfer can be changed for the internal packet. Also, the addressmanagement table includes, at least, terminal-unit-address-relatedinformation of an external IP packet, i.e. destination address andaddress mask, as registration information. The terminal unit, whoseterminal-unit address is not registered in the address management table,is excluded from communicating thereby enhancing the informationsecurity of IP communication.

[0420] 6. Embodiment 6 for Setting Entire or Part of External Addressinto Internal Frame:

[0421] In the fifth embodiment case, there existed, as internal packetaddresses, two internal addresses, i.e. a source internal address and adestination internal address. In this embodiment, the internal packet isreferred to as an internal frame. The internal frame includes adestination internal address without including a source internaladdress, in respect of -which there is a difference from the fifthembodiment. The external address in the entirety or in a part is setwithin an internal frame thereby forming an internal frame. The internalframe is in a layer less than a third layer of communication functionlayer, e.g. corresponding to a communication second layer or second anda half layer. When the address length defined as an internal frame isshort, an extension domain or extension header is provided in the frameto store a destination external address and source external address. Theinternal frame containing only a destination internal address includesan optical frame and an MPLS frame.

[0422] In FIG. 54, numeral 600 is an IP network, numerals 601 to 604 arenetwork node units, numerals 605 to 608 are routers, numerals 609 and610 are LANs, and numerals 611 and 612 are terminal units within theLAN. The terminal unit 611 is given with an IP address EA1 while theterminal unit 612 is with an IP address EA2. The network node units andthe routers are connected directly by communication lines or indirectlyby way of the routers. The logic terminal 614 at a connection pointbetween the logic communication line 613 and the network node unit 601is given with an internal address P, while the logic terminal 616 at aconnection point between the logic communication line 615 and thenetwork node unit 602 is given with an internal address Q. When an IPpacket 620 having a source address EA1 and destination address EA2,transmitted from the terminal unit 611, reaches the network node unit601, it turns into an internal frame 623 by the use of an internalrecord of an address management table 621 on a method hereinafterreferred. The internal frame 623 is forwarded from the network node unit601 to reach the network node unit 602 by way of the communication linesand routers 606, 606, 607. From the internal frame 623 reaching thenetwork node unit 602, an external packet 624 is restored. The externalpacket 624 reaches the terminal unit 612 having an IP address EA2 viathe logic communication line 615. The external packet 624 has the samecontent as the external packet 620.

[0423] Next, explanation is made on a method to form an internal packetfrom an external packet to restore an external packet from the internalpacket. This embodiment explains the external packet by an IP packetdefined under IPv4 or IPv6. However, the invention shown in thisembodiment is unchanged in its substance even if there is difference inpacket type or address length. For example, the external packet canadopt IPv6. The external IP packet 620 is examined as to whether thereexists a record of the internal address P given in the input logicterminal 614 as an internal record of the address management table 621.In the present case, there is correspondence between a record on thefirst line and a record on the second line of the address managementtable 621. AND-operation (logical product) is made on the destination IPaddress EA2 of the input external IP packet 620 and the destination IPaddress mask MK2 on the first-lined record. It is examined whether ornot the result agrees with a destination address EA2x described in thefirst-lined record, according to the below Equation (4).

IF (“EA2” AND “MK2”=“EA2x”)  (4)

[0424] Similarly, inspection is made on the second-lined recordaccording to the below Equation (5).

IF (“EA2” AND “MK3”=“EA3y”)  (5)

[0425] In the present case, the above Equation (4) is held.

[0426] Next, AND-operation is made on the source IP address EA1 of theinput external IP packet 620 and the source IP address mask MK1 on thefirst-lined record. It is examined whether or not the result agrees witha destination address EA1x existing in the first-lined record, accordingto the below Equation (6).

IF (“EA1” AND “MK1x”=“EA1x”)  (6)

[0427] In the present case, the above Equation (6) is held. From thefact that the Equations (4) and (6) are held on the first-lined record,selected is the destination internal address “Q” described in thefirst-lined record. In this manner, fixed are the internal addresses “P”and “Q” for forming an internal frame. Incidentally, where comparingbetween parts of external addresses EA2 and EA1, it is satisfactory toprovide bit “1” in a range to be compared of the masks MK2x and MK1x andbit “0” in the range excluded from the comparison. As hereinafterreferred, when forming an internal frame, because an external address isset in a part domain of an internal address, an internal address area ina range for setting an external address can be previously omitted fromthe record of the address management table 621.

[0428] In FIG. 55, a sign “X” represents an address area 626 of an IPpacket while a sign “P” represents an address area 627 of an internalframe. FIG. 56 represents that an external IP packet 630 is stored in apayload section 633 of an internal frame 631 and further a sourceaddress X and destination address Y of an external IP packet 630 arestored in a header 636 extension domain 635 in a header 632 of theinternal frame 631. The internal frame header 632 stores an internaldestination address Q.

[0429]FIG. 57 shows another method for storing an external IP packet 640in an internal frame 641. Of an external IP packet 640, the content ofthe external IP packet excepting a source address X and destinationaddress Y is stored in a payload section 643 of the internal frame 641.The payload of the internal frame, in a part 647, does not contain asource address X and destination address Y of an external IP packet 640.An internal frame header 648 stores therein an internal destinationaddress Q. FIG. 58 shows another method for storing an external IPpacket 650 in an internal frame 6451, wherein an external IP packet 650is stored in a payload section 653 of an internal frame 651. A part x ofan external address X and a part y of an external address Y are storedin an extension domain 655 of a header 656 of the internal frame 641.The header 658 of the internal frame stores an internal destinationaddress Q.

[0430] <<Summary>>

[0431] The IP network includes two or more network node units. Anexternal IP packet, in an input-sided network node unit, is convertedinto an internal packet and transferred within the IP network. In anoutput-sided network node unit, an external IP packet is restored fromthe internal packet. An internal frame contains a destination internaladdress without containing a source internal address. Also, under thecontrol of a record of an address management table in the input-sidednetwork node unit, the external address being set in the external IPpacket, in the entirety or in a part, is set within an address area ofthe internal packet. Meanwhile, the address management table includes,at least, terminal-unit-address-related information of an external IPpacket, i.e. destination address and address mask, as registrationinformation. The terminal unit, whose terminal-unit address is notregistered in the address management table, is excluded fromcommunicating thereby enhancing the information security of IPcommunication.

[0432] 7. Embodiment 7 Showing Various Functions of Network Node UnitWithin IP Network

[0433] This embodiment is concerned with the function and configurationof the network node unit 105 (FIG. 17) of the first embodiment andnetwork node unit 231 (FIG. 33) of the second embodiment.

[0434] In FIG. 59, a communication network 700-1 include network nodeunits 700-2 to 700-4. The network node units 700-2 and 700-3 includeunit control tables 700-5 and 700-6 formed by a set of various controlrecords concerning terminal-to-terminal communication connectioncontrol. An external packet 700-8 forwarded from a terminal unit 700-7is inputted to the network node unit 700-2 via a logic terminal 700-10at an end of an external communication line 700-9, and converted into aninternal packet 700-11 in a source-sided network node unit 700-2. Theinternal packet 700-11 reaches a destination-sided network node unit700-3 by way of internal communication lines 700-12 to 700-13. In thenetwork node unit 700-3, an external packet is restored. The restoredexternal packet 700-14 reaches a destination terminal unit 700-17 by wayof a logic terminal 700-15 and external communication line 700-16. Theunit control tables 700-5 and 700-6, both, are used in converting anexternal packet into an internal packet and in converting an internalpacket into an external packet. Meanwhile, the network node units 700-2to 700-3 are characterized to have a packet filter function and afunction to convert a destination address and port number (hereinafter,referred to as “multicast recipient address converting function” or“multicast NAT function) in multicast control. The packet filterfunction is to select under the control of the unit control table inconverting the external packet into the internal packet whether to ornot to pass an external packet through a network node unit. This is truefor the case to restore an external packet from an internal packetwherein selection is made under the control of the unit control tablewhether to or not to pass through a network node unit.

[0435] The external packet to be transferred by the communicationnetwork includes an IPv4 packet, an IPv6 packet and an Ethernet frame.An internal packet is applicable to an IPv4 packet, an IPv6 packet, anEthernet frame, an extension Ethernet frame, an MPLS frame, an HDLCframe, an extension-tagged external packet or the like. Furthermore,this embodiment can define and use an external packet and internalpacket, as follows. Namely, the external packet and internal packet aremade as a data block having a bit-based value to be transferred over acommunication line, to include a destination address and source address.The internal packet cannot contain a source address. Meanwhile, theinternal packet is made to include an external packet. The externalpacket has a domain to hold a source port number and destination portnumber for use in identifying an application program within a terminalunit or an apparatus (telephone set, printer or the like) for connectionto the terminal unit. Otherwise, a source port number and destinationport number may be included in a TCP or UDP segment placed in a payloadsection of the external packet.

[0436] Next, explanation is made on an embodiment that the communicationnetwork 700-1 is an IP network and both external and internal packetsare IPv4. The other packet form and communication network will beexplained in the latter half of this embodiment.

[0437] <<IP Network for IPv4 Packet Transfer>>

[0438] In FIG. 60, numeral 701 is an IP network, numerals 702 and 703are network node units, numerals 704-1 and 722 are unit control tables,and numerals 705 and 706 are terminal units having a function to sendand receive an IP packet. The terminal unit 705 is given with anexternal address EA1 while the terminal unit 706 is with an externaladdress EA2. A logic terminal 713 at a connection point between thecommunication line 707 and the network node unit 703 is given with aninternal address IA1. A logic terminal 704-2 at a connection pointbetween the communication line 708 and the network node unit 702 isgiven with an internal address IA2. An external IP packet 710 forwardedfrom the terminal unit 705 is inputted to the network node unit 703through the logic terminal 713 and via the communication line 707. Thenetwork node unit 703 uses an information processing mechanism 721 (FIG.61) and unit control table 722, to convert the external IP packet 710into an internal packet 711 (FIG. 60) and forward it onto an internalcommunication line 718. The internal packet 711 is transferred in the IPnetwork 701 to the network node unit 702 including the logic terminal704-2 given with a destination address IA2 for the internal packet 711via an internal communication line 719. The network node unit 702 usesthe information processing mechanism and unit control table includedtherein to restore an external packet 712 from the internal packet 711.This is forwarded onto the communication line 708 via the logic terminal704-2. Thus, the external packet 712 reaches the terminal unit 706.

[0439]FIG. 61 is a diagram for explaining the relationship between thenetwork node unit 703 (FIG. 60, FIG. 61) and the network node unit shownin the second embodiment (FIG. 33) and prior patent application. Arouter 724 and servers 725 to 727 are connected to the network node unit703 through communication lines 728 and 729. A control line 715 in an IPnetwork 701 is connected to the router 724. A terminal-unit gateway702-1 corresponds, for example, to the terminal-unit gateway 223-1 inthe second embodiment (FIG. 33) of the invention. The servers 725 and726 correspond to a server “TES” (telephone management server) or “TNS”(telephone number server 227-1) within the terminal-unit gateway 223-1.Note that 713 can be referred to as an external logic terminal becauseof being connected to an external communication line and 714 be referredto as an internal logic terminal because of being connected to aninternal communication line.

[0440] Furthermore, the servers 725 to 727 correspond to the telephonemanagement server or telephone number server (FIG. 197 on a thirteenthembodiment in the prior patent application). 733 is an overflow line foruse in multicast control, having a function to recover, on therecipient-sided network node unit, the IP packets sent back frommulticast recipients (e.g. FIG. 311 on a seventeenth embodiment in theprior patent application). Note that, although the prior patentapplication terms 702-1 as a terminal-unit gateway having encapsulationfunction or terminal-unit gateway, the invention refers it to as a“terminal-unit gateway”.

[0441] <<Function of Network Node Unit>>

[0442] The network node unit 703 can use a unit control table 722 (FIG.61) to carry out the following five functions. The first functionconverts an external IP packet into an internal packet (hereinafter,referred also to as “encapsulation”) and restores an external IP packetfrom the internal packet (hereinafter, referred also to as“decapsulation”). The second function is a packet filter function.Namely, conversion of from one to the other of an external IP packet andan internal packet is suppressed or not suppressed by a given selectionmethod regulated in the unit control table. In other words, an externalpacket or internal packet is allowed or not allowed, in the network nodeunit, to pass. The packet filter function is divided as a protocolfilter function and a port filter function. Also, the third functioncontrols the priority of sending into the IP network an external IPpacket inputted externally of the IP network, thus controlling thepriority to forward an internal packet arrived from the interior of theIP network toward the outside of the IP network.

[0443] Furthermore, the fourth function is divided into two. The first(multicast control 1) is to forward an IP packet having a multicastdestination address to a plurality of destinations so that, whendetecting an IP packet directed in the reverse direction, or toward themulticast data source, the IP packet can be transferred to the overflowline. The second of the fourth function (multicast control 2) is adestination address converting function (multicast recipient addressconverting function) in multicast control, to send an IP packet restoredto an individual IP address and port number of a reception-sidedterminal unit from the destination-sided network node unit. The fifthfunction is to convert an external IP packet of after being provided byan electronic signature in a payload section into an internal packet sothat an electronic signature can be provided to a payload section of anexternal packet restored from the internal packet. The five functionsare implemented with using a plurality of communication records orvarious control records set within the unit control table 722.

[0444] <<Relationship between Unit Control Table and Address ManagementTable>>

[0445] The unit control table in the prior patent used in thisembodiment includes a function of a conversion table in respect ofcontrolling IP packet encapsulation and decapsulation, and similarly afunction of an address management table used in the prior patentapplication and the other embodiment of the invention.

[0446] <<Communication Record Form>>

[0447] Numeral 738 (FIG. 62) shows a form of a communication record tomanage the major function of the network node unit. This has item namesof, from left, “ISA”, “IRA”, “NSA”, “NDA”, “MSA”, “MDA”, “IFI”, “IFE”,“ID”, “CTL” and “PTR”. The item ISA is an internal transmission IPaddress, the item IRA is an internal incoming IP address, the item NSAis a network source address, the item NDA is a network destinationaddress, the item MSA is a source IP address, the item MDA is adestination IP address mask, the item IFI is an internal logic terminalidentifier, the item IFE is an external logic terminal identifier, theitem ID is a record ID, the item CTL is record control information anditem PTR is a pointer to a sub-table.

[0448] Numeral 738X (FIG. 62) shows another form of communicationrecord. This includes a logic terminal identifier “PinID” at the extremeleft end but has the other items same as 738. The use of the logicterminal identifier helps shorten a search time for an internal address“ISA” in a communication record. In this embodiment, althoughcommunication record form is explained with 738, a form of 738X can besimilarly carried out.

[0449]FIG. 63 is an example expressing a content of a communicationrecord in a program language C, representing the items of thecommunication record “ISA”, “IRA”, “NSA”, “NDA”, “MSA”, “MDA”, “IFI”,“IFE”, “ID”, “CTL” and “PTR”. Ina control item CTL, provided are bitpositions denoting bit positions of, from left, “00”, “01”, . . . ,“31”. The bit position “00” shows a validity of the communicationrecord. The bit positions “01” to “04” show a concrete method ofprotocol filter function. The bit positions “05” to “08” show a concretemethod of port filter function. Also, the bit position “09” showswhether to carry out priority control or not. The bit position “10”shows whether to carry out multicast control 1 or not. The bit position“11” shows whether to carry out multicast control 2 or not. Furthermore,the bit position “12” shows whether to carry out transmission signaturecontrol or not. The bit position “13” shows whether to carry outreception signature control or not. The bit positions “14” to “30” areundefined domains. The bit position “31” shows whether to carry outrecord memory protect control or not.

[0450] <<First Function: Function of Encapsulation and Decapsulation>>

[0451] The first function is similar to as the IP capsulation anddecapsulation by the prior patent. Explanation is made with reference toa unit control table 722-1 (FIG. 64) and flowchart of FIGS. 65 and 66.

[0452] An external IP packet 710 (FIG. 60) has a source IP address of“EA1” and a destination IP address of “EA2”. This is inputted to thenetwork node unit 703 via a logic terminal 713 provided with an internaladdress IA1 (Step 740-1 in FIG. 65). The information processingmechanism 721 identifies the external IP packet 710 and examines whetherthere is a communication record having the acquired internal address IA1within the unit control table 722 or not (Step 740-2). In the presentcase, fallen under are the items of the record on the second line in theunit control table 722-1 (FIG. 64) (Step 740-3), wherein there are found“IA1”, “IA2”, “NSA1”, “NDA2”, “MSA1”, “MDA2”, “IF714”, “IF713”, “ID1”,“CTL1” and “PTR1”. When the item CTL of the detected record on thesecond line has a bit position “00” value “1”, the record is determinedinvalid. Thus, another record is processed. Note that, where there is nodetection of a record fallen under, the accepted external packet 710 isdumped.

[0453] When the item CTL1 of the detected record has a bit position “00”value of “0”, AND-operation is made, in 1-bit correspondence, of thedestination address EA2 of the external IP packet and the destinationmask MDA2 acquired from the record, to examine whether an operationresult agrees with a network destination address NDA2 or not (Equation(7)). Where in agreement in the operation result, AND-operation is made,in 1-bit correspondence, of the source address EA1 of the external IPpacket and the destination mask MSA1 acquired from the record, toexamine whether an operation result agrees with a network source addressNSA1 or not (Equation (8)). The above procedure is shown in Step 740-4of FIG. 65.

IF (“EA2”) AND (“MDA2”)=“NDA2”  (7)

IF (“EA1”) AND (“MSA1”)=“NSA1”  (8)

[0454] For example, in the case that the destination IP address EA2 hasa value “192.3.4.5”, the destination mask MDA2 has a value“255.255.255.0” and the destination address NDA2 has a value“192.3.4.0”, the above Equation (7) is held. Furthermore, because theabove Equation (7) is held for the case the destination IP address EA2has a value in a range of from “192.3.4.1” to “192.3.4.255”, it ishelpful in decreasing the total number of communication records. Theabove Equation (8) also is helpful in decreasing the total number ofcommunication records on the similar principle.

[0455] Furthermore, it is possible to use “MDA2”, “NDA2”, “MSA1” and“NSA1” with a value “0.0.0.0” in all of them. With this, the Equations(7) and (8) are unconditionally held regardless of values of the IPaddresses “EA2”, “EA1”. As an effect of this, because the external IPpacket is encapsulated into an internal packet regardless of theexternal IP packet destination address “EA2” and source address “EA1”, avirtual private line can be realized within the IP network 701.

[0456] Furthermore, it is possible to use “MDA2” and “MSA1” with a value“255.255.255.255” in them, “NDA2” with a value of an external IP packetdestination address “EA2”, and “NSA1” with a value of an external IPpacket source IP address “EA1”. With this, the Equations (7) and (8) areunconditionally held. Accordingly, it is possible to limit the source IPaddress “EA1” and the destination IP address “EA2” into one, i.e. to useas a record for communication between a terminal having an IP address“EA1” and a terminal having an IP address “EA2”. The communicationrecord in a conversion table in the prior patent has a form having amask value “255.255.255.255”.

[0457] When the Equations (7) and (8) are both held, an internal packet711 is formed that has a destination internal address IA2, the seconditem of the record, taken as a destination address and an internaladdress IA1 taken as a source address (Step 740-7). This is forwardedonto the internal communication line 718 via an internal logic terminal714 to be identified by an internal logic terminal interface IF714, arecord seventh item (Step S740-10). Incidentally, in the aboveprocedure, the Step S740-5 (packet filter control), the Step S740-6(signature provision), the Step S740-8 (transmission priority control)and Step S740-9 (multicast control) shown in FIG. 65 are optionsselectable to carry out and not to carry out. The above procedure usesan example not to be selected.

[0458] The forwarded internal packet 711 is transferred within the IPnetwork 701 by the use of a destination internal address IA2 of withinthe internal packet 711, reaching the network node unit 702. The networknode unit 702 uses an information processing mechanism and unit controltable contained therein to restore an external packet 712 from theinternal packet 711. The restored external packet 712 is forwarded ontothe communication line 708 via the logic terminal 704-2 (FIG. 60). Theexternal packet 712 reaches the terminal unit 706.

[0459] Next, explanation is made on external IP packet transfer of fromthe terminal unit 706 to the terminal unit 705. The external IP packethaving a source external address EA2 and destination external addressEA1, forwarded from the terminal unit 706, is transmitted over thecommunication line 708 and inputted to the network node unit 702 via theexternal logic terminal 704-2. An internal packet is formed andtransferred within the IP network 701, then reaching the internal nodeunit 703. The internal packet contains an external IP packet in itspayload section. This is an internal source address IA2 and internaldestination address IA1 of the internal packet.

[0460] From now on, explanation is made using FIG. 66. The internalpacket is inputted to the network node unit 703 via the internal logicterminal 714 (FIG. 61) (Step S741-1). The information processingmechanism 721 at the inside of the network node unit 703 examineswhether or not there exist a communication record having aninternal-packet destination internal address IA1 in the unit controltable 722-1 (Step S741-2). In the present case, fallen under is theitems of a record on the second line of the unit control table 722-1(Step 741-3). Note that, when there is no detection of a record fallenunder, an accepted internal packet is dumped. When the item CTL of adetected record has a bit position “00” value of “0”, AND-operation isthen made, in 1-bit correspondence, of the destination address EA1 ofthe external IP packet contained in the payload of the internal packetand the destination mask MSA1 acquired from the second-lined record, toexamine whether an operation result agrees with a network source addressNSA1 or not (Equation (9)). Where agreement in the operation result,AND-operation is made, in 1-bit correspondence, of the source addressEA2 of the external IP packet contained in the internal packet and thedestination mask MSA2 acquired from the second-lined record, to examinewhether an operation result agrees with a network source address NDA2 ornot (Equation (10)).

IF (“EA1”) AND (“MSA1”)=“NSA1”  (9)

IF (“EA2”) AND (“MDA2”)=“NDA2”  (10)

[0461] When the Equations (9) and (10) are both held, the external IPpacket is taken out of the payload section of the internal packet(restoring an external IP packet). The restored external IP packet isforwarded onto the external communication line 707 via an external logicterminal 713 to be identified by an external logic interface IF713, aneighth item of the second-lined communication record. The restoredexternal IP packet reaches the terminal 705. Incidentally, in the aboveprocedure, the step S741-5 (packet filter control) shown in FIG. 66 isthe second function of the network node unit, the step S741-6 (signatureprovision) is the fifth function of the network node unit, the stepS741-8 (arrival priority control) is the third function of the networknode unit and the step S741-9 (multicast control) is the fourth functionof the network node unit. This is the case not to carry out them.

[0462] <<Relationship Between Main Table and Sub-Table>>

[0463]FIG. 67 explains a method of making reference to various controlrecords as sub-tables of a unit control table from a communicationrecord 742-1 as a main table of the unit control table. Namely, thepointer item 742-2 at the last of the communication record stores thepointers representative of whereabouts of a sub-table of filter controlrecord 742-3, a sub-table of priority control record 742-4, a sub-tableof multicast control record 742-5 and a sub-table of signature controlrecord 742-6. How to use the sub-tables will be described later.Incidentally, the filter control record is explained with an example offurther separation with a protocol control record and a port controlrecord. However, unless the filter control record is separated with aprotocol control record and a port control record, the invention in itssubstance is not changed.

[0464] <<Second Function-1: Protocol Filter>>

[0465] The second packet filter function is divided as a protocol filterfunction and a port filter function. The filter control record isdivided as a protocol control record and a port control record. Theprotocol filter comprises four forms of protocol filters (protocolfilters 1 to 4) to be designated with a bit position “01” to “04” at aninside of communication-record control item CTL (in FIG. 63). Theprotocol control record for designating a protocol filter 1 to 4 has aform 743 (FIG. 68) as a record having a length of (n+1) bytes andcomprising (n+1) -items each having 1 byte. The extreme left itemrepresents the number of protocols to be described in this record. Thefollowing items, in the number of “n”, include protocol representativevalues (8 bits) in the number of n defined under TCP/IP art.

[0466] The protocol filter 1 defines a protocol for allowing an internalpacket, formed from an external IP packet by the network node unit, tobe transmitted into the IP network (referred to as transmissionpermission). For example, 743-1 allows the external IP packets of threeprotocols, i.e. protocol-numbers “1”, “6” and “17”, to pass the networknode unit and be transmitted as internal packets. The external IPpackets having the other protocol number than those are to be discarded.The protocol filter 2 defines an external IP packet protocol forallowing an external packet restored by the network node unit from aninternal IP packet arrived from the inside of the IP network to beforwarded toward an outside of the IP network (referred to as arrivalpermission). For example, 743-2 allows the restored external IP packetsof two protocols, i.e. protocol-numbers “6” and “17”, to be forwardedfrom the network node unit. The external IP packets having the otherprotocol number than them are to be discarded.

[0467] The protocol filter 3 defines a protocol for blocking, by thenetwork node unit, an internal packet formed from an external IP packetfrom being transmitted into the IP network (referred to as “transmissionblocking”). For example, with 743-3, the external packets of twoprotocols, i.e. protocol-numbers “8” and “89”, are discarded. Theexternal packets having the other protocol number than them are to beconverted into an internal packet and thereafter transmitted. Theprotocol filter 4 defines an external IP packet protocol for blocking,by the network node unit, an external packet restored from an internalIP packet arrived from the inside of the IP network from being forwarded(referred to as “arrival blocking”). For example, with 743-4, therestored external IP packets of three protocols, i.e. protocol-numbers“1”, “8” and “89”, are discarded. The external IP packets having theother protocol number than them are allowed to pass the network nodeunit.

[0468] The communication record adopts a rule not to simultaneouslydesignate the protocol filter 1 and the protocol filter 3. However, whensimultaneously designated, the network node unit can be defined foroperation to designate only either one of the protocol filter 1 or theprotocol filter 3. Similarly, the communication record adopts a rule notto simultaneously designate the protocol filter 2 and the protocolfilter 4. However, when simultaneously designated, it is possible todesignate only either one of the protocol filter 2 or the protocolfilter 4.

[0469] <<Second Function-2: Port Filter>>

[0470] The port filter comprises four forms of port filters (portfilters 1 to 4) to be designated with a bit position “05” to “08” at aninside of the communication-record control item CTL. The port controlrecord, for designating a port filter 1 to 4, has a form 744 (FIG. 69)of a record having a length of (2n+2) bytes and comprising (n+1) itemseach having 2 bytes. The extreme left item represents twice (2n) thenumeral of port number described in the record. The following items, inthe number of 2n, define the sections of port representative values (16bits) under TCP/IP art, including n pairs comprising port number uppervalue and port number lower value.

[0471] The port filter 1 allows to transmit an internal packet having anexternal-IP-packet source port number (transmission permission source(origin) port number) in a payload section of an internal packet formedfrom an external IP packet, and designates a destination port number(arrival permission destination port number) allowing an external packetrestored from an internal IP packet to be forwarded to an outside of theIP network. The principle of division of source port number anddestination port number is in accordance with the TCP-communicationclient server model rule that the source port number used intransmission and the destination port number used in arrival are in thesame value. For example, 744-1 designates three port number sections,i.e. port number of from 100 to 200, port number of from 500 to 600 andport number of from 4000 to 5000. This port number is an external IPpacket source port number in a payload section of an internal packet tobe transmitted into the IP network (transmission permission source portnumber) or a destination port number of an external packet restored froman internal IP packet (arrival permission destination port number). Theexternal IP packet or internal packet having a port number of other thana designated condition is blocked from passing the network node unit.The port filter 2 allows to transmit an internal packet having aexternal-IP-packet destination port number (transmission permissiondestination port number) in a payload section of an internal packetformed from an external IP packet, and designates an external-IP-packetsource port number (arrival permission source port number) allowing anexternal packet restored from an internal IP packet to be transmitted toan outside of the IP network. For example, 744-2 designates two portnumber sections, i.e. port number of from 20 to 21 and port number offrom 80 to 80. This port number is a transmission permission destinationport number or arrival permission source port number. The external IPpacket or internal packet having a port number of other than adesignated condition is blocked from passing the network node unit.Meanwhile, in the case the port filter 1 and the port filter 2 aredesignated with the same port number range, the two designations areboth effective, resulting in impossible to distinguish whether attransmission or arrival. Also, it is not distinguished whether the portnumber is a destination port number or a source port number. In both,the packet is allowed for passing.

[0472] The port filter 3 blocks from being transmitted an internalpacket having an external-IP-packet source port number (transmissionprevention source port number) in a payload section of an internalpacket formed from an external IP packet, and designates anexternal-IP-packet destination port number (arrival blocking source portnumber) blocking an external IP packet restored from an internal IPpacket from being forwarded to an outside of the IP network. Forexample, 744-3 designates three port number sections, i.e. port numberof from 25 to 30, port number of from 53 to 60 and port number of from80 to 80. This port number is a transmission prevention source portnumber or arrival prevention destination port number. The external IPpacket having a port number of other than a designated condition is notprevented but converted into an internal packet and transmitted into theIP network, or forwarded as a restored external packet onto the externalcommunication line.

[0473] The port filter 4 is, for the network node unit, to prevent frombeing transmitted an internal packet having an external-IP-packetdestination port number (transmission prevention destination portnumber) in a payload section of an internal packet formed from anexternal IP packet, and to designate an external-IP-packet source portnumber (arrival prevention source port number) preventing an external IPpacket restored from an internal IP packet from being forwarded to anoutside of the IP network. For example, numeral 744-4 designates threeport number sections, i.e. port number of from 25 to 25, port number offrom 53 to 200 and port number of from 12000 to 13000. This port numberis a transmission prevention destination port number or arrivalprevention source port number. The external IP packet having a portnumber of other than a designated condition passes the network nodeunit. Meanwhile, when the port filter 3 and the port filter 4 are bothdesignated, the two designations are both effective, resulting inimpossible to distinguish whether at transmission or arrival. Also, itis not distinguished whether the port number is a destination portnumber or a source port number. In both, the packet is prevented frompassing. Incidentally, in the above case preventing an external IPpacket from passing in the port filter 1 to port filter 4, upontransmission, communication record search is resumed at step S740-2(FIG. 65) while, upon arrival, communication record search is resumed atstep S741-2 (FIG. 66). Note that, in designating both permission andprevention to the protocol filter, it is possible to define effectiveonly for permission.

[0474] IP address provides a function to identify terminal, and portnumbers can identify application program in terminal or gadgetsconnected. A pair of IP address and port number are called socket. Theport filter can provide secure socket communication between terminals.The functions of the protocol filter and port filter described above canbe carried out upon forming an internal packet from an external packet(Step 740-5 in FIG. 65) and upon restoring an external packet from aninternal packet (Step 741-5 in FIG. 66).

[0475] <<Relationship Between Protocol Filter and Port Filter>>

[0476] In the protocol filter, the measure is properly defined and usedfor the case a TCP or UDP including a port number is designated withoutdesignating a port filter. For example, when the protocol filter l(transmission permission) is designated, TCP or UDP transmission isdefined to allow transmission regardless of a port number value. Whenthe protocol filter 2 (arrival permission) is designated, TCP or UDPtransmission is defined to allow arrival regardless of a port numbervalue. When the protocol filter 3 (transmission prevention) isdesignated, TCP or UDP transmission is defined to prevent transmissionregardless of a port number value. When the protocol filter 4 (arrivalprevention) is designated, TCP or UDP transmission is defined to preventarrival regardless of a port number value.

[0477] In a case that the protocol filter and the port filter are bothdesignated, when an IP packet a protocol filter is applied is preventedor deleted, the IP packet to which the port filter is to be applied isconsidered not existing. Meanwhile, it is possible to define such thatport filter designation is effective only in the case the higher-orderprotocol of an IP packet, a subject of application, is TCP or UDP whilethe IP packet is deleted when the higher-order protocol is other thanTCP or UDP.

[0478] Furthermore, as a case not to separate the filter control recordwith a protocol control record and a port control record, it is possibleto define and use a filter control record capable of designating such acondition that, for example, upon transmission a protocol number value17 only is allowed and destination port number values 3000 and 80 andsource port number value 25 are allowed while, upon arrival, a protocolnumber value 17 only is allowed and source port number values 3000 and80 and source port number value 25 are allowed.

[0479] <<Third Function: Packet Priority Control>>

[0480] Packet priority control is designated with a bit position “09” inthe communication record control item CTL. A priority “0” to “7” isprovided by designating a port number, wherein priority is increased asthe numeral increases.

[0481]FIG. 70 explains an overall flow of packet priority control.Numeral 746 is an IP network, numerals 747-1 to 747-3 are network nodeunits, and numerals 748-1 to 748-5 are terminal units. An external IPpacket 750-1 is forwarded from the terminal unit 748-1, an external IPpacket 750-2 is forwarded from the terminal unit 748-2, and external IPpackets 750-3 and 750-4 are forwarded from the terminal unit 748-3.These four external IP packets reach the network node unit 747-1 nearlyat a same time. The network node unit 747-1 forwards, by itstransmission priority control function, internal IP packets 751-1, 751-3and 751-2 in the order onto an internal communication line 749-1, and aninternal IP packet 751-4 onto an internal communication line 749-2.Herein, the internal IP packets 751-1 to 751-4 are formed from theexternal IP packets 750-1 to 750-4. The transmission priority forforwarding the internal IP packets is defined based on each internalcommunication line, by the use of a priority control record. The detailwill be described later.

[0482] Next, explanation is made on a flow of arrival priority control.Internal IP packets 751-6 and 751-7 arrive the network node unit 747-2via an internal communication line 749-3 while internal IP packets 751-8and 751-9 arrive the network node unit 747-2 via an internalcommunication line 749-4. These four internal IP packets reach thenetwork node unit 747-2 nearly at the same time. The network node unit747-2, by its reception priority control function, forwards external IPpackets 752-8, 752-7 and 752-9 in the order onto an internalcommunication line 753-1, and an external IP packet 752-6 onto anexternal communication line 753-2. Herein, the external IP packets 752-6to 752-9 have been restored from the internal IP packet 751-6 to 751-9.The arrival priority for forwarding the external IP packets is definedbased on each internal communication line, by the use of a prioritycontrol record. The detail will be described later.

[0483] As a method to designate a port number defining a transmissionpriority, defined are a priority control type “0” and a priority controltype “1”. The type “0” is to designate a source port number upontransmission and a destination port number upon arrival. The type “1” isto designate a destination port number upon transmission and a sourceport number upon arrival. The principle of division between source portnumber and destination port number is in accordance with theTCP-communication client server model rule for dividing between sourceport number and destination port number.

[0484]FIG. 71 represents a priority control record form 754-1. Thisrecord comprises three items storing a flag, a protocol and a portnumber. FIG. 72 represents the priority control record in a programlanguage C with somewhat greater detail. The flag is 8 bits. A flag bitposition “0” represents whether the record continues or not. A bitposition “1” divides between priority control type “0” and prioritycontrol type “1”. Bit positions “2” to “4” represents basic prioritieswhile bit positions “5” to “7” represents contract priorities.

[0485]FIG. 73 shows another priority control table 755 comprising threepriority control records. The priority control record on the first lineis an example of the priority control type “0”, having a basic priority“1”, a contract priority “2”, a protocol 6 (TCP) and a port number“4096”. The priority control record on the second line is an example ofthe priority control type “1”, having a basic priority “1”, a contractpriority “4”, a protocol 6 (TCP) and a port number “1024”. The prioritycontrol record on the third line is an example of the priority-controltype “0”, having a basic priority “1′, a contract priority “3”, aprotocol 17 (UDP), wherein designation for a port number is not made.Because the flag on the third line has a continuation bit “0”, there isno priority control record on the following fourth line.

[0486] In transmission priority control of among the above prioritycontrols, a priority provided for an internal packet to be formed isdefined due to the designation by the priority control table 755 (Step740-8 in FIG. 65). In arrival priority control, a priority provided foran external packet to be restored is defined due to designation by thepriority control table 755 (Step 741-8 in FIG. 66).

[0487] <<Fourth Function-1: Multicast Control Function-1>>

[0488] The first function of multicast control function is designatedwith a bit position “10” in the communication-record control item CTL.In the present case, the bit position “10” in the control item CTL isset in value “1”. In FIG. 74, numeral 757 is an IP network, numerals758-1 and 758-2 are network node units, and numerals 759-1 to 759-5 areterminal units.

[0489] First, explanation is made on a multicast control function upontransmission. An external IP packet having a multicast destination isforwarded from the terminal unit 759-1 to reach the network node unit758-1 via the communication line, thereby reaching Step S740-9 by way ofa series of steps S740-1 to 740-8 shown in FIG. 65. Thereupon, becauseof setting “1” in the bit position “10” value in thecommunication-record control item CTL, the network node unit 758-1 looksan MC control record 764-1 (FIG. 75) and knows internal logic terminalidentifiers “3” and “4”. Designation is made to forward the internalpacket formed from the external IP packet in step S740-7 (FIG. 65) ontoan internal communication line 760-3 identified by the internal logicterminal identifier “3”, and designation is made to forward it onto aninternal communication line 760-4 identified by the internal logicterminal identifier “4”. Thereupon, in Step S740-10, the formed internalpacket is forwarded onto the internal communication lines 760-3 and760-4. Incidentally, the MC control record form includes the number ofinternal logic terminal identifiers “n” and internal identifiers IFI-j(j=1, 2, . . . n) in the number of “n”, as shown at 764-2. Invariation,the internal logic terminal identifier “3” may be previously set withinthe internal logic terminal identifier IFI of the communication recordand the internal logic terminal identifier “4” only be set in the MCcontrol record, to use the internal logic terminal identifiers “3” and“4”. Meanwhile, in a case that the value of the control item CTL bitposition “10” is “0”, the multicast control function will not operate.Thus, the internal packet is forwarded onto an internal communicationline defined by the internal logic terminal identifier IFI of thecommunication record.

[0490] Next, explanation is made on the multicast control function uponarrival. An internal IP packet having a multicast destination istransferred in the IP network 757 to reach the network node unit 758-2via an internal communication line 761, thereby reaching Step S741-9 byway of a series of Steps S741-1 to S741-8 shown in FIG. 66. Thereupon,because of setting “1” in the bit position “10” value in thecommunication-record control item CTL, the network node unit 758-2 looksan MC control record 764-3 (FIG. 76) and knows external logic terminalidentifiers “3”, “4” and “5”. Designation is made to forward theinternal packet restored from the internal IP packet in step S741-7(FIG. 66) onto an external communication line 762-3 identified by theexternal logic terminal identifier “3”, designation is made to forwardit onto an external communication line 762-4 identified by the externallogic terminal identifier “4” and further designation is made to forwardit onto an external communication line 762-5 identified by the externallogic terminal identifier “5”. Thereupon, the restored internal packet,in Step S741-10, is forwarded onto the external communication lines762-3 and 762-5.

[0491] Incidentally, the external-logic-terminal identifier controlrecord form includes the number of external logic terminal identifiers“n” and internal identifiers IFE-j (j=1, 2, . . . n) in the number of“n”, as shown at 764-4. In variation, the internal logic terminalidentifier “3” may be previously set within the external logic terminalidentifier IFE of the communication record to use the external logicterminal identifier “3” set therein. Meanwhile, in a case that the valueof the control item CTL bit position “10” is “0”, the multicast controlfunction will not operate. Thus, the restored external packet isforwarded onto an external communication line defined by the externallogic terminal identifier IFE of the communication record.

[0492] <<Overflow Line Control>>

[0493] In FIG. 74, when an external IP packet, having as a destinationaddress an address “MA” same as a destination multicast address “MA”contained in an IP packet transferred from the network node unit 758-2to the terminal units 759-3 to 759-5, is inputted from the externalcommunication lines 762-3 to 762-5 to the network node unit 758-2, ifthe internal logic terminal identifier IFI of the communication record764-5 is set in value “0” (FIG. 77), the inputted multicast external IPpacket is not formed into an internal packet in the network node unit758-2 but transferred onto the communication line 762-2 while remainingin an external IP packet form.

[0494] <<Fourth Function-2: Multicast Control Function-2>>

[0495] The second function of multicast control (destination addressconverting function in multicast, multicast NAT function) is designatedwith a bit position “11” in the communication-record control item CTL(in FIG. 63). In the present case, the bit position “11” in the controlitem CTL is set in value “1”.

[0496]FIG. 78 shows a form of a second control record 765-1 in multicastcontrol. The first item in the left is “n”, the second item “Sub-1”, thethird item “sub-2”, . . . , and the (n+1) -th item “sub-n”. The firstshows the number of sub-items, and the second to (n+1)-th show sub-itemsin the number of “n”. Numeral 765-2 shows a more-detailed definitionthan that of the sub-items, having “IFE-j”, “port-j” and “IP-j”. Aterminal unit having an IP address of IP-j is connected to acommunication line having an external logic terminal identifier IFE-j.The terminal unit is represented using a port number “port-j” to receivemulticast data.

[0497] In FIG. 79, numeral 766-1 is an IP network, numerals 766-2 and766-3 are network node units, and numerals 764-4 to 765-8 are terminalunits. The terminal unit 766-4 has an IP address “IP-x”, the terminalunits 766-5 to 766-8 have respective IP addresses of “IP-1”, “IP-2”,“IP-3” and “IP-4”. At first, the terminal unit 766-4 forwards anexternal IP packet 766-10 having a source IP address “IP-x”, source portnumber “port-x”, destination multicast IP address “M-IP” and destinationport number “M-port” (Step S768-1 in FIG. 82). The external IP packet766-10 passes over the communication line and further through thenetwork node unit 766-2 where it is applied by an encapsulation functionand turned into an internal packet 766-11. The internal packet 766-11has a transmission internal address “ISA1” and arrival internal address“IM-IP”. The internal packet 766-11, in its payload section, is anexternal IP packet 766-10. At this time, the internal packet 766-11 istransferred over an internal communication line of the IP network 766-1(Step S768-2) to reach the network node unit 766-3, reaching Step S741-9by way of a series of Steps S741-1 to S741-8 shown in FIG. 66. Thecommunication record, on the first line from above in a unit controltable 766-30 (FIG. 81) in the network node unit 766-3, is used indecapsulation. However, it is the relevant communication record “IM-IP”,“ISA1”, “NSA30”, “NDA30” and “. . . ”. The communication-record controlitem CTL on the first line has a bit position “11” value set to “1”.Because a second capsule control record 766-23 (FIG. 80) has “4” in thefirst item from left, sub-items are four in the number.

[0498] According to the designation “IFE-1”, “port-1”, “IP-1” in thefirst sub-item 766-24, an external packet 766-12 having a destinationexternal IP address IP-1 and destination port number port-1 is formedfrom the internal packet 766-11. The external packet 766-12 is forwardedonto a communication line 766-9 having an external logic terminalidentifier IFE-1 (Step S768-5 in FIG. 82). The external packet 766-12has a source IP external address “M-IP” and source port number “M-Port”,wherein the source IP address M-IP and source port number M-Port istransferred from a destination external IP address M-IP and destinationport number M-Port for an external IP-packet 766-10 in a payload sectionof the internal packet 766-11. The destination IP address of theexternal IP packet 766-12 uses an IP address “IP-1” unique to a terminalunit 766-5 to be connected to the external logic terminal identifierIFE-1.

[0499] Subsequently, according to the content “IFE-2”, “port-2”, “IP-2”of a sub-item 766-25 of a multicast second control record, an externalIP packet having a source address M-IP and source port number M-port isforwarded to the terminal unit 766-6 having an IP address IP-2 connectedto the external logic terminal identifier IFE-2 (Step S768-6). From nowon, similarly, according to the content “IFE-3”, “port-3”, “IP-3” of asub-item 766-26, an external IP packet having a source address M-IP andsource port number M-port is forwarded to the terminal unit 766-7 havingan IP address IP-3 connected to the external logic terminal identifierIFE-3 (Step S768-7). Subsequently, according to the content “IFE-3”,“port-4”, “IP-4” of a sub-item 766-27, an external IP packet having asource address M-IP and source port number M-port is further forwardedto the terminal unit 766-8 having an IP address IP-4 connected to theexternal logic terminal identifier IFE-3 (Step S768-8). Herein, it ispossible to connect a plurality of terminals 766-7 and 766-8 to acommunication line designated by the external logic terminal identifierIFE-3. By the above procedure, the terminals 766-5 to 766-8 end thereception of multicast data.

[0500] The terminal units 766-5 to 766-8, after receiving multicastdata, can report of a reception or answer to the multicast datatransmission terminal unit 766-4 and multicast transmission managementterminal 767-7. Explanation is made on an example to reply from theterminal unit 766-5. The terminal unit 766-5 forms an external IP packet767-1 (in FIG. 83) and forwards it onto the communication line 766-9(Step S768-10 in FIG. 82). The external IP packet 767-1 has an IPaddress and a port number respectively exchanged with in source anddestination with the IP address and port number of a received externalIP packet 766-12 (in FIG. 79). Namely, they are the source IP addressIP-1 and source port number port-1 and the destination IP address M-IPand source port number M-port of the external IP packet 767-1.

[0501] The external IP packet 767-1 is turned into an internal packet767-2 (in FIG. 83) by the use of a record “IS5, IS73, NSA5, NDA5, . . .” on the fourth line of the unit control table 766-30 in the networknode unit 766-3, and forwarded onto the internal communication line767-4 to reach the network node unit 766-3 (Step S768-11). This isdecapsulated by the application of a communication record “IS73, IS5,NDA5, NSA5, . . . ” on the seventh line of the unit control table 766-30(FIG. 81). The restored external packet reaches the terminal unit 767-3via a communication line 767-5 defined by the logic terminal identifierIFE13 of the communication record (Step S768-12).

[0502] The multicast data proxy terminal unit 767-3 forms an IP packetincluding the content of an answer packet received from the terminalunit 766-5 and sends the IP packet to the multicast data sendingterminal unit 766-4 (Steps S768-14 to S768-16 in FIG. 82). At this time,used is a communication record “IS73, IS64, . . . ” on the eighth lineof the unit control table 766-30. Furthermore, the multicast dataresponse proxy terminal unit 767-3 can send an IP packet containing theanswer to the multicast data transmission management terminal unit 767-7(Step S768-18 to S768-20). At this time, used is a communication record“IS73, IS67, . . . ” on the ninth line of the unit control table 766-30.The terminal unit 767-3 has a function to handle an answer from theterminal unit 766-6 to 766-8 similarly to an answer from the terminalunit 766-5. Furthermore, it can receive all the answers from theterminal units 766-5 to 766-8 and send them collectively in one IPpacket.

[0503] <<Fifth Function: Signature Function>>

[0504] The signature control function is designated with a bit position“12” to “13” in the communication-record control item CTL (in FIG. 63).In the present case, the bit positions “12” and “13” in the control itemCTL are set in value “1”. In FIG. 84, numeral 770-1 is an IP network,and numerals 770-2 and 770-3 are network node units, numerals 770-4 and770-5 are terminal units. An external IP packet 770-6 is forwarded fromthe terminal unit 770-4 to reach the network node unit 770-2 via acommunication line, reaching Step S740-6 by way of a series of StepsS740-1 to S740-5 shown in FIG. 65. In Step S740-6, because of setting“1” in the bit position “12” value in the communication-record controlitem CTL, signature function and parameters are acquired from asignature control record 771 (FIG. 85) to be made reference to from therelevant communication record. Using a signature function section770-12, provided is a signature 770-9 for the payload section of theexternal packet 770-6. Then the process proceeds to the next StepS740-7.

[0505] Next, explanation is made on a signature providing function uponarrival. An internal IP packet is transferred in the IP network to reachthe network node unit 770-3, reaching Step S741-6 by way of a series ofSteps S741-1 to S741-5 shown in FIG. 66. In Step S741-6, because ofsetting “1” in the bit position “13” value in the communication-recordcontrol item CTL, signature function and parameters are acquired from asignature control record to be made reference to from the relevantcommunication record. Using a signature function section 770-13,provided is a signature 770-10 for an external-packet 770-6 payloadsection existing in a payload section of the internal packet. Then theprocess proceeds to the next step S741-7.

[0506] The signer can be a common carrier operating and managing the IPnetwork 770-1. The signature 770-9 and signature 770-10 can contain atime the packet 770-6 and 770-7 passes the network node unit. Note thatthe signature function section 770-12 and 770-13 can be implemented asinternal hardware of the network node units 770-2 and 770-3 or a programmodule. Meanwhile, a signature function server can be provided and usedconnected to the network node unit.

[0507] <<Separation within IP Network>>

[0508] The IP network can be separated into a plurality of internalnetworks by a method of transferring an internal packet into the networkaccording to a port number value in an external IP packet. Withreference to FIGS. 86 and 87, explanation is made on a method toseparate the IP network into a plurality of internal IP networks byusing a communication record and port filter function. Numeral 772-1 isan IP network, numerals 772-2 to 772-6 are IP networks within the IPnetwork 772-1. Numerals 773-1 to 782-4 are LANs, numerals 772-7 to 772-8are terminal-unit gateways, numerals 774-1 and 774-2 are network nodeunits, numerals 774-3 and 774-4 (FIG. 87) are memory areas includingunit control tables, 775-5 to 775-6 are unit control tables comprising aplurality of communication records, and 776-1 to 776-6 a report filtercontrol records (one of unit control table elements).

[0509] <<Separation Within IP Network-1: Telephone Network Case>>

[0510] An external IP packet having a source IP address EA1 anddestination IP address EA2 is forwarded from the terminal unit 773-5 topass over the communication line 773-9 and inputted to the network nodeunit 774-1 via a logic terminal 773-30 given with an internal address11. The IP packet has a payload of a UDP segment, in which case a sourceport number thereof is “5004” and a destination port number is “5008”.In the present case, the record on the first line is fallen excludingthe record representing a title of a unit control table 775-5. Thefirst-lined record has, from left, “I1”, “I2”, “N1”, “N2”, “M1, “M2”,“G2”, “F1”, “ID1” and “CT1”. An internal address 11, provided to thelogic terminal 773-30 the external packet has been inputted, is thefirst item I1 in the communication record. A result of AND-operation, ina 1-bit correspondence, of the destination address EA2 of the externalIP packet by a destination mask M2 acquired from the record agrees withan network address N2 of the communication record. Furthermore, a resultof AND-operation, in a 1-bit correspondence, of the source address EA1by a destination mask M1 agrees with a network destination address N1,in this case. In the present case, the IP packet has passed anaddress-condition inspection in respect of the first-lined communicationrecord.

[0511] Next, designated are a port filter control record 776-1 and portfilter control record 776-2 related from the communication record. Theport filter control record 776-1 is a designation for a port filter 1when the bit position “05” value in the communication-record “CTL”domain is “1”, thus designating that a source port number attransmission and destination port number at arrival is within a portnumber section of 5000-5100. This case is a case that an external IPpacket is converted into an internal packet and transmitted into the IPnetwork, wherein a source port number “5004” of the external IP packetexists within the port number section “5000”-“5100”.

[0512] Similarly, the port filter control record 776-2 is a designationof a port filter 2 because the bit position “06” value in thecommunication-record “CTL” domain is “1”, designating that a source portnumber at arrival and destination port number at transmission is withina port number section of 5000-5100. This case is a case that an externalIP packet is converted into an internal packet and transmitted into theIP network, wherein a destination port number “5008” of the external IPpacket exists within the port number section “5000”-“5100”. Namely, theinputted external IP packet passes an address-condition inspection inrespect of the communication record, to satisfy the condition of portnumber section on the port filter control record 776-1 and port filtercontrol record 776-2. Accordingly, the external IP packet conditionsatisfies the condition of being converted into an internal packet. Theinternal packet formed by the above is forwarded onto the internalcommunication line 773-14 of an internal logic terminal identifier itemG2 of the communication record.

[0513] Next, explanation is made on the relationship between theinputted external IP packet and the communication record on the secondline of the unit control table 775-5 excluding the record representing atitle. The second-lined communication record has items of, from left,“I1”; “I2”, “N1”, “N2”, “M1”, “M2”, “G1”, “F1”, “ID2” and “CT2”. Theexternal IP packet passes an address-condition inspection in respect ofalso the second-lined communication record. Next, the port filtercontrol record 776-3 related from the communication record has acommunication-record “CTL” domain bit position “06” value of “1” andhence a designation for the port filter 2, designating that a sourceport number at arrival and destination port number at transmission iswithin a port number section of 4000-4100. This case is a case oftransmission into the IP network. Because an external-IP-packetdestination port number “5008” does not exist within the port numbersection “4000”-“4100”, it is prevented to form an internal packet fromthe external IP packet and transfer it into the IP network.

[0514] Furthermore, the external IP packet cannot be formed into aninternal packet because of not satisfying the condition of encapsulationin respect of the other record of the unit control table 775-5. Theinternal packet formed using the first-lined communication record istransferred into the IP network 772-3 via an internal communication line773-14 identified by the internal logic terminal identifier G2, to reachthe network node unit 774-2 via an internal communication line 773-18.Within the network node unit 774-2, the unit control table 775-6 has, onthe first line excluding the record representing a title, “I2”, “I1”,“N2”, “N1”, “M2”, “M1”, “H2”, “F2”, “ID4” and “CT4”, from left. Thus,this record passes an address-condition inspection, and the port filterrecords 776-4 and 776-5 are applied on the similar principle as the portfilter control records 776-1 and 776-2. By the above method, an externalIP packet is restored from the internal packet to reach the terminalunit 773-7 via a communication line 773-1. In the case of reversedtransmission direction, i.e. in transmission of from the terminal unit773-7 to the terminal unit 773-5, a communication record and port filtercontrol record is used in the similar way to the above, effecting thecommunication through the IP network 772-3.

[0515] A telephone set is connected inside the terminal unit 773-5, anda port number “5004” is provided to the telephone set. A telephone setis connected inside the terminal unit 773-7, and a port number “5008” isprovided to the telephone set. In the present case, the source portnumber “5004” and “5008” within an external packet adopts an SIPcommunication protocol, one of a technique for the IP telephone. Thetelephone set within the terminal unit 773-5, for conversion of voiceinto a digital voice and storing it within the IP packet, has a UDPsegment in a payload section of the IP packet. A source port number isgiven with “5004” and a destination port number is with “5008”, to senda digital voice packet toward the terminal 773-7. The telephone setwithin the terminal unit 773-7 restores an analog voice from a receiveddigital voice.

[0516] The telephone communication by the above method is to be effectedexclusively through the internal IP network 772-3. The internal IPnetwork 772-3 is used as a telephone communication private network.Incidentally, as TCP or UDP communication technique is known a techniquethat a plurality of application program including a telephone programare set up within one terminal unit wherein the terminal unit has one IPaddress and different individual port numbers are assigned to theapplication programs to transmit and receive an IP packet with theapplication program similarly included in another terminal unit.

[0517] <<Separation Within IP Network-2: Quality Network Case>>

[0518] This is the case that the application program within the terminalunit 773-5 operates as a client while the application program within theterminal unit 773-7 operates as a server. The server has a port number“4000” to “4100”. However, a client port number cannot be previouslydefined. An external IP packet having a source IP address EA1 anddestination IP address EA2. is forwarded from the terminal unit 773-5and inputted to the network node unit 774-1 by way of the communicationline 773-9 and a logic terminal 773-30 given with an internal address11. The external IP packet has a payload of TCP segment having adestination port number of “4000” to “4100”. In the present case,candidates are a record on the first line of a unit control table 775-5and a record on the second line thereof. The first-lined communicationrecord has, from left, “I1”, “I2”, “N1”, “N2”, “M1”, “M2”, “G2”, “F1”,“ID1” and “CT1”. Thus, the first-lined communication record passes anaddress-condition inspection. The port number section, defined by portfilter control records 776-1 and 776-2 related from the communicationrecord, designates to be within a port number section 5000-5100 at bothtransmission and reception and both in source and destination. In thepresent case, the external IP packet forwarded from the terminal unit773-5, having a destination port section of “4000” to “4100”, does notsatisfy the condition of port number section. Thus, the external packetis not converted into an internal packet.

[0519] Next, the second-lined communication record has, from left, “I1”,“I2”, “N1”, N2”, “M1”, “M2”, “G1”, “F1”, “ID2” and “CT2”. Thus, therelevant communication record passes an address-condition inspection.The communication record has a “CTL”-domain bit position “06” of a value“1”. Consequently, designation is to the port filter 2. The port numbersection, defined by the port filter control record 776-3, designates adestination port number section at transmission of 4000-4100, hencesatisfying the condition and being converted into an internal packet.The internal packet is forwarded onto an internal communication line773-13 for an seventh item G1 of the second-lined communication record,and transferred within the IP network 772-2 to reach the network nodeunit 774-2 via an internal communication line 773-17. In the networknode unit 774-2, a unit control table 774-2 has the second-lined recorditems of, from left, “I2”, “I1”, “N2”, “N1”, “M2”, “M1”, “H1”, “F2”,“ID5” and “CT5”, from left. This communication record passes anaddress-condition inspection, and the communication record has a“CTL”-domain bit position “05” value of “1”. Consequently, designationis to the port filter 1. The port filter control record 776-6 is appliedby a destination port number section at arrival of “4000” to “4100”.Thus, an external IP packet is restored from the internal packet, whichreaches the terminal unit 773-7 via a communication line 773-11.

[0520] In the case reverse in communication direction to the above, i.e.when an external IP packet is sent from the terminal unit 773-7 to theterminal unit 773-5 (note that the source port number in an IP-packetTCP segment is “4000” to “4100”) and converted into an internal packetin the node network unit 774-2. In transmitting the internal packet, theport filter control record 776-6 is applied by the source port numbersection at transmission of “4000” to “4100”. Consequently, the internalpacket is transferred to the network node unit 774-1 by way of theinternal communication line 773-17, IP network 772-2 and internalcommunication line 773-13. When the network node unit 774-1 receives theinternal packet to restore an external IP packet, the port filtercontrol record 776-3 is applied by a source port number section attransmission of “4000” to “4100”.

[0521] In brief, the terminal units 773-5 and 773-7 use telephone setsconnected respectively to carry out telephone communication within aport number section of “5000” to “5100”. The application program on theterminal unit 773-7 operates as a server applied by a port number “4000”to “4100”. The other application programs on the terminal unit 773-5operate as a client using the application program on the terminal unit773-7. At this time, a telephone-communication internal network 772-3 isused in telephone communication, and an internal network 772-2 is usedin the communication between the client and the server. Thecommunication lines 773-9 and 773-11 are commonly used in telephonecommunications and client-server communication. The internal network772-3 as a telephone network is reduced in the number of router stages(also called the number of hops) for delay reduction. The internalnetwork 772-2 as a client-server communication network can be reduced incommunication failure and offered as a quality network assuringcommunication quality.

[0522] <<Separation within IP Network-3: Multicast Network Case>>

[0523] Explanation is made on a method that an application program inthe terminal unit 773-5 is operated as a multicast transmission serverwhile the application program in the terminal unit 773-7 is operated asone person of a plurality of users who receives the multicast dataforwarded from the multicast transmission server. In the present case,an IP packet for multicast transmitted from the terminal unit 773-5 isinputted to the network node unit 774-1 via the communication line773-9, wherein used is the third-lined record of a unit control table775-5. The third-lined record has, from left, “I1”, “Im”, “N1m”, N2m”,“M1m”, “M2m”, “G3”, “F1”, “ID3” and “CT3”. In the case that the inputtedmulticast external IP packet passes an address-condition inspection, amulticast internal packet is formed. The internal packet is forwardedonto the communication line 773-15 designated by an item G3.

[0524] From then on, it reaches the network node unit 774-2 by way of amulticast internal network 772-4 and communication line 773-19. Becausethe multicast external IP packet has a destination address as an IPaddress inherent to multicast, the internal packet will not betransferred to the internal network 772-2 or internal network 772-3 bythe address-condition inspection. The internal packet reaches thenetwork node unit 774-2 where the third-lined record of the unit controltable 775-6 is used. The third-lined record has, from left, “Im , “I1”,“N2m”, “N1m”, M2m”, “M1m”, “0”, “F2”, “ID6” and “CT6”. A multicastexternal packet is restored from the internal packet. The restoredexternal packet is delivered to the terminal 773-7 via a communicationline 773-11 designated by the item F2.

[0525] <<Separation Within IP Network-4: Best-Effort Network Case>>

[0526] Explanation is made on an IP communication method using aninternal network 772-5 between the terminal unit 773-6 and the terminalunit 773-8.

[0527] The internal network 772-5, different from the foregoing internalnetwork, is a best-effort network as an IP network to suppresscommunication fee instead of assuring communication quality. Theterminal 773-6 is given with an address EA7 while the terminal 773-8 iswith an address EA8. The address EA7 uses a value different from everyIP address used within the LAN 773-1 to be connected to thecommunication line 773-9. Similarly, the address EA8 is different fromevery IP address used within the LAN 773-4 to be connected to thecommunication line 773-12. For an external IP packet having a source IPaddress EA7 and a destination IP address EA8 to be inputted to thenetwork node unit 774-1 from the terminal unit 773-6 via thecommunication line 773-9, the communication record satisfying anaddress-condition inspection is solely the fourth-lined record in theunit control table 775-5. An internal packet, formed by using acommunication record having record items of “I1”, “I8”, “N7”, “N8”,“M7”, “M8”, “G4”, “F1”, “ID7” and “CT7”, is forwarded onto acommunication line 773-16 designated by the item G4.

[0528] From then on, the internal packet reaches the network node unit774-2 by way of the internal network 772-5 and further communicationline 773-20. In the network node unit 774-2, the fourth-lined record ofthe unit control table 775-6, i.e. “I8”, “I1”, “N8”, “N7”, “M8”, “M7”,“H4”, “F8”, “ID8” and “CT8”, is used in a decapsulation method. Arestored IP packet reaches the terminal unit 773-8 via the communicationline 773-12. An external IP packet in a reverse direction to the above,i.e. external IP packet forwarded from the terminal unit 773-8 to theterminal unit 773-6, reaches the terminal unit 773-6 by way of thecommunication line 773-20, best-effort network 772-5 and communicationline 773-16 in a way similar to the foregoing. The server 727-1 in theterminal-unit gateway 772-7 and the server 727-2 in the terminal-unitgateway 772-8 shown in FIG. 71 are allowed to communicate by sending andreceiving an IP packet by way of the router 724-1, communication line715-1, internal network 772-6, communication line 715-2 and router724-2.

[0529] <<Another Method for Referring to Control Record FromCommunication Record>>

[0530]FIG. 88 explains another method to find, out of a communicationrecord 777-1, a filter control record 777-3, a priority control record777-4, a multicast control record 777-5 or a signature control record777-6. In this embodiment, the pointer item 777-2 at the last of thecommunication record 777-1 stores all the pointers representative ofrespective whereabouts of a filter control record 777-3, a prioritycontrol record 777-4, a multicast control record 777-5 and a signaturecontrol record 777-6. FIG. 89 explains still another method to find, outof a communication record 778-1, a filter control record 778-3, apriority control record 778-4, a multicast control record 778-5 or asignature control record 778-6. Using a communication record ID 778-7within the communication record 778-1, a record ID 778-2 has a contenthaving a value of the communication record ID 778-7. By combining therecord ID 778-7 with the pointer 778-8 to show whereabouts of thecontrol records 778-3 to 778-6, individual control records 778-3 to778-6 can be found out of the communication record 778-1 through therecord ID 778-2.

[0531] <<Another Form of Communication Record>>

[0532] When carrying out the first function of the network node unit,i.e. encapsulation and decapsulation, in the case that the values of“MDA2” and “MSA1” are both given with “255.255.255.255” in the Equations(7) and (8), the two masks can be omitted. The communication record 779(FIG. 90) is a communication record omitting the items MSA and MDA inthe communication record 738 (FIG. 62).

[0533] <<Another Form of External and Internal Packets>>

[0534] In the above, the external IP and the internal packets are bothexplained with the example with IPv4. Next, another example is explainedthat the external packet adopts an IPv6 packet, an Ethernet frame or thelike while the internal packet employs an IPv6 packet, an Ethernetframe, an extension Ethernet frame, an MPLS frame, an HDLC frame, ortagged frame. Although, in the above, the address was an IP addresshaving an IPv4 32-bit length, the address is changed to an IPv6 address,MAC address or HDLC address due to packet or frame change. Furthermore,for the internal address of an internal packet or a hereinafter-referredextension tag, explanation is made on a case with two addresses and acase with one address.

[0535] <<Another Embodiment that Internal Packet Contains Source andDestination Addresses>>

[0536]FIG. 91 shows a manner that an external IP packet 781-11 isforwarded from the terminal unit 781-2 having an address EA1 onto acommunication line 781-6, the external IP packet 781-11 being convertedinto an internal packet 781-12 (FIG. 92) within the network node unit781-4 of the IP network 781-1 and transferred in the IP network 781-1,an external IP packet 781-13 being restored from the internal packet781-12 in the network node unit 781-5, the restored external IP packet781-13 reaching the terminal unit 781-3 having an address EA2 via acommunication line 781-9. The internal packet 781-12, in a payload,contains at least the external IP packet 781-11. The logic terminal781-7 at an end of the communication line 781-6 is given with aninternal address IA1 while the logic terminal 781-8 at an end of thecommunication line 781-9 is given with an internal address IA2. In thepresent case, the internal packet 781-12 is in an IPv6 form. Theinternal packet 781-12, in a header, contains two internal addresses IA1and IA2. Numeral 781-10 is a router having at least an IPv6 packettransfer function. In the communication record 780 (FIG. 93), the firstitem ISA from left is an IPv6 internal source address having a 128-bitlength. The second item IRA from left is an IPv6 internal destinationaddress having a 128-bit length. The other items are the same as thecommunication record 738 (FIG. 62), wherein the principle ofencapsulation and decapsulation is the same.

[0537] In the above explanation with reference to FIGS. 91 to 93, theexternal IP packet can be in any of the IPv4 packet form or the IPv6packet form. Incidentally, in the case of the IPv6 packet form, of amongthe communication record 780 the third to sixth items, i.e. “NSA”,“NDA”, “MSA and “MDA”, each have a length as long as 128 bits.

[0538]FIG. 94 shows a manner that an external IP packet 784-11 isforwarded from the terminal unit 784-2 having an address EA1 onto acommunication line 784-6, the external IP packet 784-11 being convertedinto an internal packet 784-12 (FIG. 95) in the network node unit 784-4and transferred within the IP network 784-1, an external IP packet784-13 being restored from the internal packet 784-12 in the networknode unit 784-5, the restored external IP packet 784-13 reaching theterminal unit 784-3 having an address EA2 via a communication line784-9. The internal packet 784-12, in a payload, contains at least theexternal IP packet 784-11. The logic terminal 784-7 at an end of thecommunication line 784-6 is given with an internal address IA1 while thelogic terminal 784-8 at an end of the communication line 784-9 is givenwith an internal address IA2. In the present case, the internal packet781-12 is characterized in a MAC frame to contain two internal addressesIA1 and IA2. The internal packet 784-12 is a MAC frame, and numeral784-10 is a router capable of transferring a MAC frame. Incidentally,when using a MAC frame or MPLS frame having three or less layeredcommunication functions, the packet may be also called a frame. In thecommunication record 783 (FIG. 96), the first item ISA from left is aninternal transmission MAC address having a 48-bit length. The seconditem IRA from left is an internal destination MAC address having a48-bit length. The other items are the same as the communication record738 (FIG. 62), wherein the principle of encapsulation and decapsulationis the same.

[0539] A protocol kind in a header of an external IP packet 784-11 isused for the foregoing protocol filter function as a second function ofthe network node unit. Namely, reference is made to a protocol kind in aTCP or UDP segment in the external IP packet 784-11 under the control ofa communication record 783 (FIG. 96) of in the unit control table. Aselected external IP packet turns into an internal frame (internalpacket). Under the control of the unit control table in the network nodeunit 784-7, reference is made to a protocol kind in the TCP or UDPsegment in the external IP packet in the internal frame to restore anexternal IP packet (protocol filter). Meanwhile, a port number in theTCP or UDP segment placed in a payload section of the external IP packet784-11 is used for the port filter function. Namely, under the controlof the communication record 783, reference is made to a port number in aTCP or UDP segment of an external IP packet. A selected external IPpacket turns into an internal frame (port filter). Under the control ofa unit control table, reference is made to a port number of a TCP or UDPsegment in the external IP packet of the internal frame. An external IPpacket is restored from a selected internal frame.

[0540]FIG. 97 shows a manner that an external IP packet 791-11 isforwarded onto a communication line 791-8 from the terminal unit 791-2having an address EA1, the external IP packet 791-11 being convertedinto an internal packet 791-12 in the network node unit 791-3 andtransferred within the IP network 791-1, in the network node unit 791-4an external IP packet 791-13, being restored from the internal packet791-12, the restored external IP packet 791-13 reaching the terminalunit 791-5 having an address EA2 via a communication line 791-9. Theinternal packet 791-12 is formed having an extension tag 791-15 added tothe external IP packet 791-11. The extension tag 791-15 is a data blockincluding at least two internal addresses. The internal address isdefined in a proper length on an internal rule of the IP network 791-1,e.g. 20 bits, 32 bits or 48 bits. An internal address IA1 is provided toa logic terminal 791-6 at an end of a communication line 791-8. Aninternal address IA2 is provided to a logic terminal 791-7 at an end ofa communication line 791-9. In the present case, the extension tag791-15 forming the internal packet 791-12 is characterized including twointernal addresses IA1 and IA2. Numeral 791-10 is a router capable oftransferring the internal packet 791-12. The communication record 792-1(FIG. 98) has the first item ISA, from left, that is a domain to storean internal source address as the internal address IA1. The second itemIRA, from left, is a domain to store an internal destination address asthe internal address IA2. The other items are the same as thecommunication record 738 (FIG. 62). The extension tag 791-15 can includethe information other than the internal address, e.g. priority of aninternal packet to pass the router 791-10 (DiffServ router priority,etc.). Furthermore, the communication record 792-1 can be designed toinclude priority field, and the priority in the record 792-1 can becopied into the internal packet 791-12 when generated.

[0541] Summarizing the embodiment of FIGS. 91 to 98, in the case that anexternal packet is inputted from a logic terminal on an externalcommunication line. In case that, three sets of a source-sided logicterminal identifier (internal address or identifier of a logic terminalgiven with an internal address), a source external address in theexternal packet and a destination external address are defined, atransfer-destination internal address of an internal packet is definedunder the control of a unit control table of within a source-sidednetwork node unit. Incidentally, in case two sets of source-sided logicterminal identifying information and a destination external address ofin the external packet are defined, variation is possible such that atransfer destination internal address of the internal packet is definedunder the control of the unit control table of within the source-sidednetwork node unit.

[0542] <<Embodiment of Internal Packet Including Only DestinationAddress>>

[0543]FIG. 99 shows a manner that an external IP packet 791-41 isforwarded onto a communication line 791-28 from the terminal 791-22having an address EA1, the external IP packet 791-41 being convertedinto an internal packet 791-42 in the network node unit 791-23 andtransferred within the IP network 791-21, in the network node unit791-24 an external IP packet 791-43 being restored from the internalpacket 791-42, the restored external IP packet 791-43 reaching theterminal unit 791-25 having an address EA2 via a communication line791-29. The internal packet 791-42 is formed having an extension tag791-33 provided to the external IP packet 791-41. The extension tag is adata block including destination internal addresses. The internal packet791-42 (in FIG. 99) is different from the internal packet 791-12 (inFIG. 97) in respect of including a destination internal address IA2 butnot including a source internal address IA1. The internal address isdefined in a proper length on an internal rule of the IP network 791-21,e.g. 20 bits, 32 bits or 48 bits. An internal address IA1 is provided toa logic terminal 791-26 at an end of a communication line 791-28. Aninternal address IA2 is provided to a logic terminal 791-27 at an end ofa communication line 791-29. Numeral 791-40 is a router capable oftransferring the internal packet 791-42. The communication record 792-2(FIG. 100) has the first item ISA, from left, that is a domain to storean internal source address as the internal address IA1. The second itemIRA, from left, is a domain to store an internal destination address asthe internal address IA1. The communication record 791-2 is used informing an internal packet 791-40 from the external packet 791-41.

[0544] The other items of the communication record 792-2 are similar tothe communication record 738 (FIG. 62). The principle of encapsulationand decapsulation is also similar. The extension tag 791-33 can includethe information other than an internal address, e.g. priority of aninternal packet to pass the router 791-40 (DiffServ router priority,etc.).

[0545]FIG. 101 shows a manner that an external MAC frame 792-11 isforwarded onto a communication line 792-8 (FIG. 101) from the terminalunit 792-2 having an MAC address EA1 having a 48-bit length, theexternal MAC frame 792-11 being converted into an internal MAC frame792-12 in the network node unit 792-3 and transferred within an Ethernetnetwork 792-1, in the network node unit 792-4 an external MAC frame792-13 being restored from the internal MAC frame 792-12, the restoredexternal MAC frame 792-13 reaching the terminal unit 792-5 having an MACaddress EA2 via a communication line 792-9. The internal MAC frame792-12 (FIG. 102) includes an extension tag 792-15. The other framedomains are in the same form as the MAC frame 792-11. The external MACframe 792-11 includes, in its information domain, an external IP packet792-16 to be forwarded from the terminal unit 792-2 to the terminal unit792-5.

[0546] The protocol kind in a header of an external IP packet 792-16 canbe used for a protocol filter function as a second function of thenetwork node unit. Namely, reference is made to a protocol kind of an IPpacket 792-16 in an external frame 792-11 under the control of acommunication record 792-20 (FIG. 103) in the unit control table. Aselected external frame 792-11 turns into an internal frame 792-12.Furthermore, reference is made to a protocol kind of the IP packet792-16 in the external frame 792-11 in the internal frame 792-12, torestore an external frame 792-13. Meanwhile, a port number in a TCP orUDP segment placed in a payload section of an IP packet 792-16 is usedfor the port filter function on the basis of the above method.Incidentally, the extension tag can employ, for example, a VLAN tagstandardized under IEEE802.1Q.

[0547] An internal address IA1 is provided to a logic terminal 792-6 atan end of a communication line 792-8 (FIG. 101). An internal address IA2is provided to a logic terminal 792-7 at an end of a communication line792-9. The extension tag 792-15 can include, as internal destinationaddress, any one of internal addresses IA1 and IA2. 791-10 is a routercapable of transferring the internal MAC frame 792-12. The communicationrecord 792-2 (FIG. 103) has the first item ISA, from left, of aninternal address IA1. The second item IRA, from left, is an internaladdress IA2. The internal MAC frame 792-12 includes, as a destinationinternal address, a second item value IA2 of the communication record792-20. Meanwhile, in the network node unit 792-3, an internal MAC framearrives from the internal of an Ethernet network 792-1. When restoringan external MAC frame, the first item IA1 of the communication record792-20 is used to examine whether the destination internal address ofthe arrived MAC frame is an address IA1 or not. The communication record792-20 (FIG. 103) is in the same form as the communication record 738(FIG. 62). For example, mask operation is made on the external MACaddress on the same principle as the Equations (1) and (2). Furthermore,used are protocol information in the external-IP-packet header in theexternal MAC frame or a source port number and destination port numberin a TCP or UDP packet of a payload section of the external IP packet.In a case that the external packet is an Ether frame, a protocol kind inan IP packet 792-16 in the Ether frame can be used to carry out aprotocol filter function. Furthermore, a port number in a TCP or UDPsegment in an IP packet in the Ether frame can be used to carry out aport filter function or multicast NAT function.

[0548]FIG. 104 shows a manner that an external IP packet 793-11 isforwarded onto a communication line 793-7 from the terminal unit 793-2having an address EA1, the external IP packet 793-11 being convertedinto an internal frame 793-12 in the network node unit 793-5 andtransferred within a communication network 793-1, in the network nodeunit 793-6 the internal frame 793-12 is restored into an external IPpacket 793-13 that reaches the terminal unit 793-3 having an address EA2via a communication line 793-9. An internal address IA1 is provided to alogic terminal 793-4 at an end of the communication line 793-7. Aninternal address IA2 is provided to a logic terminal 793-5 at an end ofthe communication line 793-9. In the present case, the header of theinternal frame 793-12 is characterized by an MPLS frame header includinga destination internal address IA2. The internal address corresponds toan MPLS label (e.g. 20 bits). The MPLS label employs an MPLS labelmultiplex technique capable of adding other MPLS labels one afteranother. The communication record 794 (FIG. 105) is in the same form asthe communication record 738 (FIG. 62). Furthermore, the internal frame793-12 may include priority for transport. The communication record 794can be designed to include priority field, and the priority in therecord 794 can be copied into the internal frame 793-12 when generated.

[0549]FIG. 106 shows a manner that an external IP packet 795-21 isforwarded onto a communication line 795-10 from the terminal unit 795-2having an address EA1, the external IP packet 795-21 being convertedinto an internal frame 795-22 in the network node unit 795-5 andtransferred within a communication network 795-1, in the network nodeunit 795-6 an external IP packet 795-23 is restored from the internalframe 795-22 that reaches the terminal unit 795-3 having an address EA2via a communication line 795-12. An internal address IA1 is provided toa logic terminal 795-7 at an end of the communication line 795-10. Aninternal address IA2 is provided to a logic terminal 795-8 at an end ofthe communication line 795-12. The internal frame can be made, forexample, by an optical frame using an HDLC address. Numeral 795-11 is arouter capable of transferring the internal frame 795-22. The header ofthe internal frame 795-11 is characterized by including a destinationinternal address IA2. Also, can be included a priority for transferringan internal frame. The communication record 796 (FIG. 107) is in thesame form as the communication record 738 (FIG. 62). The communicationrecord 796 has the first item ISA, from left, that is a domain to storean internal source address as the internal address IA1. The second itemIRA, from left, is a domain to store an internal destination address asthe internal address IA2. The internal address IA1 is used in restoringan external packet from the internal packet transferred from the networknode unit 795-7 into the IP network 795-1 to reach the network node unit795-8. The other items of the internal IP packet are the same as thecommunication record 738 (FIG. 62). Furthermore, the communicationrecord 796 can be designed to include priority field, and the priorityin the record 796 can be copied into the internal frame 795-22 whengenerated.

[0550] <<Variation of Address Inspection within Network Node Unit>>

[0551]FIG. 222 shows the communication records 797-15-1 and 797-15-2different from 738X (in FIG. 62) in unit-control-table communicationrecord form. The communication records 797-15-1 and 797-15-2 are thecommunication records having a form excluding the second item “ISA” andthird item “IRA” from the communication record 738X. This embodiment ischaracterized in that the internal packet 797-12 form in a communicationnetwork 797-1 (FIG. 223) is the same as the external packet 797-11 formin the communication network 797-1 and furthermore communication network797-1 internal and external addresses are given with addresses on aunified standard. The terminal unit 797-2 has an address “EA1” while theterminal unit 797-5 has an IP address “EA2”. The packet is, for example,in a form of IPv4 or IPv6. The address is, for example, a unified globalIP address.

[0552] An external packet 797-11 forwarded from the terminal unit 797-2is inputted onto the communication network 797-1 from a logic terminal797-6 via a communication line 797-8, to search, in the network nodeunit 797-3, for a communication record given with a logic terminalidentifier “Pin-ID1” for identifying a logic terminal 797-6. When acommunication record 797-15-1 is found in the network node unit 797-3,AND-operation is made, in a 1-bit correspondence, on a destinationaddress “EA2” of the external IP packet 797-11 and a destination mask“MDA2” acquired from the record, to examine whether an operation resultagrees with the network destination address “NDA2” or not (Equation(11)). In the case of agreement in the operation result, AND-operationis made, in a 1-bit correspondence, on a source address “EA1” of theexternal IP packet 797-11 and a destination mask “MSA1” acquired fromthe record, to examine whether an operation result agrees with thenetwork source address “NSA1” or not (Equation (12)).

IF (“EA2”) AND (“MDA2”)=“NDA2”  (11)

IF (“EA1”) AND (“MSA1”)=“NSA1”  (12)

[0553] When the Equations (11) and (12) are both not held, the externalpacket 797-11 is discarded. When held, the external packet 797-11 isselected. The external packet 797-11 is rendered as an internal packet797-12 without change.

[0554] The internal packet 797-12, selected by an address inspectionusing the registration information in the network node unit using theEquations (11) and (12), is transferred in a direction toward thedestination address “EA2” of the internal packet 797-12. As a result, itpasses the router 797-10 in the communication network 797-1 to reach thenetwork node unit 797-4. The internal packet 797-12 reached is appliedby a communication record 797-15-2 of the network node unit 797-4, andapplied by an address inspection similar to the foregoing. An externalIP packet 797-13 selected and obtained passes a logic terminal 797-7 toreach the terminal unit 797-5 having an address “EA2” via acommunication line 797-9. However, calculation is with reversed sourceand destination addresses. The address inspection by the Equations (11)and (12) is similar to the address inspection by the Equations (7) and(8). It is possible to omit one of the address inspection in asource-sided network node unit and the address inspection in adestination-sided network node unit.

[0555] With this configuration, it is easy to avoid such DOS attack asintensively sending insignificant garbage packets to the terminal units797-5, thus improving the security of packet transmission and reception.This embodiment, although not carrying out the first function of thenetwork node unit (capsulation and decapsulation), can carry out theother all functions, i.e. the second function (packet filter function),the third function (packet priority function), the fourth function(multicast control) and the fifth function (signature function). Thesecond to fifth functions were explained in this embodiment.

[0556] The embodiment on FIGS. 222 and 223 is summarized as follows. Thecommunication network includes two or more network node units. A packetis inputted through a logic terminal at an end of the externalcommunication line 1 into the network node unit. The packet, selected byan address inspection using the registration information in network nodeunit, is transferred within the communication network in thesource-sided network node unit. The packet reaches a destination-sidednetwork node unit where it is again subjected to an address inspectionusing network-node-unit registration information and forwarded onto anexternal communication line 2 via the logic terminal. The address in theexternal packet and the address in the internal packet use the addressesconforming to the same standard. An encapsulation and decapsulationfunction is not made but at least packet filter function, packetpriority control, multicast control and signature function are carriedout thereby improving the information security of communication network.

[0557] <<Billing Using Record ID of Communication Record>>

[0558] The ninth item ID of the communication record 738 (FIG. 62) is arecord ID to be used for identifying one record from another record. Forexample, the record ID can be used to specify a record of subject inorder for the server 725 (FIG. 61) to read out or rewrite variouscontrol records of within the unit control table 722. Also, the controlrecord can be specified for use in imposing communication fee. Also, byrewriting the first bit (FIG. 63) value in the tenth item CTL of thecommunication record 738 from “0” to “1”, the first function(encapsulation and decapsulation) of the relevant network node unitmaking reference to the communication record can be temporarily stopped.Meanwhile, because the first bit value-can be returned to “O” to returnthe network-node-unit first function to the normal operation, it ispossible to temporarily shut down the communication of acommunication-fee defaulter, for example.

[0559] <<Communication-Record Memory Protect Bit>>

[0560] The tenth item CTL last bit (FIG. 63) in the communication record738 is a memory protect bit to allow or prohibit the rewrite of thecommunication record. When the memory protect bit is “1”, the relevantcommunication record is prohibited from being rewritten. When “0”, thecommunication record is allowed to be rewritten. Memory protection canbe carried out in cooperation with a hardware function of within thenetwork node unit 703 (FIG. 61).

[0561] Summarizing the embodiment on FIGS. 99 to 107, in case that anexternal packet is inputted at a logic terminal on an externalcommunication line and three sets are defined of source-sided logicterminal identifying information, external-packet source externaladdress and destination external address, an internal communication linefor internal packet transfer is defined between source-sided anddestination-sided network node units under the control of the unitcontrol tables of within the source-sided and destination-sided networknode units and the control table of a relay unit. Where the internalpacket is applied with an MPLS frame, the internal communication linecan be considered as an internal path. Incidentally, by defining the twosets of source-sided logic terminal identifying information andexternal-packet destination external IP address, variation is possibleto provide such that an internal communication line for internal packettransfer is defined under the control of the unit control tables in thesource-sided and destination-sided network node units and the controltable in the relay unit.

[0562] <<Summary>>

[0563] The communication network includes two or more network nodeunits. An external packet turns into an internal packet under thecontrol of a unit control table in the network node unit. The internalpacket is transferred within the communication network and restored asan external packet under the control of the unit control table of thedestination-sided network node unit. The unit control table includesrespective one or more communication records including external IPaddress related information used in the terminal-to-terminalcommunication outside the communication network and address relatedinformation contained in an internal packet. An external IP packetforwarded from an external terminal unit is inputted from a logicterminal at an end of an external communication line. Using a sourceinternal address given to the source logic terminal, source-sidedexternal IP address and destination external IP address in the externalIP packet, and a unit-control-table communication record in thesource-sided network node unit; a destination internal address of theinternal packet is defined. The above address handling includes afunction of the address inspection. The internal packet is transferredwithin the communication network to reach a destination-sided networknode unit. An external IP packet is restored by the use of aunit-control-table communication record in the destination-sided networknode unit and delivered to another terminal unit via another externalcommunication line. The transfer destination of the internal packet canbe made different by the difference in an external-IP-packet destinationexternal address value. In the communication record, in the case thatthe set is even the same of internal transmission IP address ISA,network source address NSA and source IP address mask MSA, it ispossible to change the set of network destination address NDA,destination IP address mask MDA and internal destination IP address IRA,resulting that the transferred point of the internal packet is changed.

[0564] The basic function of the network node unit is to encapsulate anexternal IP packet and forward it into the IP network, decapsulate aninternal packet and forward it to an outside of the IP network and blockan IP packet having an unregistered address. More specifically, thenetwork node unit has, as a function of upon transmission, a function toconvert an external IP packet into an internal IP packet when the threesets of an internal address given to the logic terminal at a contactbetween the external communication line and the network node unit, anexternal source IP address and an external destination IP addresscontained in an external IP packet inputted from the externalcommunication line are includes in one of communication records of aunit control table in the network node unit.

[0565] Furthermore, the network node unit includes at least one ofprotocol filter function and port filter function. The protocol filterfunction controls, as a function of upon transmission, whether to or notto convert the external IP packet into an internal packet, according toa protocol in the inputted external IP packet. The port filter function,as a function of upon arrival, allows an internal packet to arrive fromthe inside of the IP network, restores an external packet from theinternal packet according to an external-IP-packet port number containedin a payload section of the input internal IP packet, and controlswhether to forward it onto an external communication line or not. Also,the port filter function controls whether to or not to restore anexternal packet from the internal IP packet according to anexternal-IP-packet port number contained in a payload section in theinputted internal IP packet. The unit control table has therein aplurality of communication records. By changing an external destinationaddress, the transfer destination of an internal packet can be changed.An IP communication network can be architected such that, under thecontrol of the unit control table, reference is made to a protocol kindof the external packet so that a selected external packet is turned intoan internal packet while an not-selected external packet is discarded.

[0566] The network node unit has a function of upon transmission todetermine a destination internal address of an internal packet when theset of external source IP and external destination IP addressescontained in an external IP packet inputted from an externalcommunication line agrees with an address inspection of a communicationrecord in a unit control table of within the network node unit. Also,the set of source and destination internal addresses of an internalpacket can specify an internal communication line to transfer theinternal packet. Furthermore, the function of converting an external IPpacket in a network node unit into an internal packet and the functionof reverse conversion can be carried out as a program within the networknode unit. The function of converting an external IP packet into aninternal packet and the function of reverse conversion can be carriedout as a function circuit within the network node unit.

[0567] The packet filter function of the network node unit includes thefunctions of a protocol filter using a protocol kind in an external IPpacket and of a port filter using a port number in a payload (such asTCP/UDP) of the external IP packet. The protocol filter allows a packetto pass or blocks a packet from passing according to a protocol passingcondition of an external IP packet entering the network node unit. Theport filter, also, allows a packet to pass or blocks a packet frompassing according to a protocol passing condition of an IP packetentering the network node unit. Using a filtering control table,function is provided both upon transmission and upon arrival.

[0568] Of the functions of the network node unit, packet prioritycontrol, multicast control-1 and -2 and signature function areselectable options. The transmission priority control function in packetpriority control is to control the priority in receiving an IP packetfrom an external communication line and in transmitting an IP packetinto the IP network from the network node unit. The arrival prioritycontrol function is a function to control the priority in allowing an IPpacket to arrive the network node unit from the inside of the IP networkand in transmitting it onto an external communication line. Both casesuse a packet priority control table. Multicast control-1 is a functionto forward a packet having a multicast address to a plurality ofdestinations and detect and recover a packet in the reverse direction(overflow line control), using a multicast control table. Multicastcontrol-2 is a function to convert a destination multicast IP addressinto another IP address (multicast recipient address conversionfunction). More specifically, it is possible to transmit an externalpacket restored through conversion of from a destination-sided networknode unit into an IP address and port number individual of a receptionterminal unit. Signature control is to provide, as a transmissionsignature function, a signature with time when an external packet passesa source-sided network node unit and to provide, as an arrival signaturefunction, a signature with time to an external packet restored in adestination-sided network node unit. A signature control table is used.

[0569] By using a communication record and port filter, the IP networkcan be separated into a plurality of internal networks. An externalpacket turns into an internal packet under the control of a unit controltable. The internal packet is transferred to a different internalnetwork according to a port number in a payload (such as TCP/UDP) of theexternal IP packet. The internal networks can be set up two or more. Theinternal packet is restored into an external packet in adestination-sided network node unit. This method enables communicationbetween two terminal units. Furthermore, on the basis of this method,the IP network can be separated into a plurality of internal networks.

[0570] A communication network can be architected such that, under thecontrol of a unit control table, reference is made to a port number in apayload of an external packet so that a selected external packet isturned into an internal packet while a not-selected external packet isdiscarded. A communication network can be architected such that, underthe control of a unit control table, reference is made to a port numberin a payload of an internal packet so that an external packet isrestored from a selected internal packet while a not-selected internalpacket is discarded. A communication network can be architected having aparticular-packet exclusion function to designate a protocol or portnumber for excluding an IP packet, by using a protocol filter 4(blocking a designated protocol upon arrival) function, a port filter 3or port filter 4 (blocking a designated port number) function.

[0571] By using a record ID in a communication record to specify arelevant communication record, it is possible to impose communicationfee. Also, it is possible to temporarily cease or recover the functionof encapsulation and decapsulation using a relevant communication recordby using a record effective bit in the communication record, for an IPnetwork. In a case that an external packet is an Ether frame, a protocolkind in an IP packet within the Ether frame can be used to carry out aprotocol filter function. Furthermore, using a port number in a payloadof an IP packet in an Ether frame, it is possible to carry out a portfilter function or multicast control 2 function. The internal packet canbe made by any of an IPv4 packet, an IPv6 packet, an Ethernet frame, anextension Ethernet frame, an MPLS frame, an HDLC frame and an externalpacket with extension tag. The communication record has internal sourceIP address, internal destination IP address, network source address,network destination address, source IP address mask, destination IPaddress mask, internal logic terminal identifier, external logicterminal identifier, record ID, record control information and IPencapsulation and decapsulation function, and includes, as sub-tables,filtering control table, packet priority control table, multicastcontrol table and signature control table. The control table functioncan be realized as a network node unit, a communication function circuitor further a communication-function programming module.

[0572] The communication network variation is possible that the formatof external packet and the internal packet are the same in the networkusing the address inspection in network node units. It is possible thatthe address administration table (FIG. 40 to FIG. 42) described in theembodiment 3 can be replaced with the unit control table (FIG. 136 orFIG. 62) described in the embodiment 7. Further variation, the unitcontrol table described in FIG. 222 for the address inspection can beimplemented in the Embodiment 3.

[0573] <<Relation to Conventional Inventions>>

[0574] The major part of the invention is in the packet filter function,the multicast recipient address conversion function (multicast NATfunction) and the IP network inside separation using port numbers. Thebasic portion of encapsulation and decapsulation (first function) isdisclosed in Embodiment 1 of the prior patent, the basic portion ofpriority control (third function) is in Embodiments 32 and 33 of theprior patent, the basic portion of multicast-control overflow line(fourth function-1) is in Embodiments 17 and 18 of the prior patent, andthe basic portion of signature control is in Embodiments 21 of the priorpatent. The present invention discloses a method of carrying out acombination of the packet filter and multicast NAT functions with theother function, wherein external and internal packets are disclosedwithin various embodiments.

[0575] 8. Embodiment 8 for Carrying Out Fixed Telephone Set, MobilePhone and Multimedia Communication on the Same IP Network:

[0576] In FIG. 108, an IP communication network 900 includesterminal-unit gateways 901-1 to 901-5. Fixed telephone sets 905-1 to905-4 are connected to any of media routers 903-1 to 903-4 throughrespective wired communication lines. Mobile phones 905-5 to 905-8 areto be connected to any of respective radio base points 902-1 to 902-4through respective radio communication lines. It is not fixed whether toconnect the mobile phone 905-5 to 905-8 to any radio base point. Themedia router and radio base point is connected to any of network nodeunits via a communication line having an IP packet transfer function.Numerals 905-10 to 905-17 are terminal units having an IP packettransmission/reception function, each connected to the media routerthrough respective communication lines.

[0577] Numeral 915 is an operation management server of the IPcommunication network 900, which is connected to the router 911-1 viathe communication line. The mobile phone can be as any of a voicetelephone set, an image-input/output-functioned telephone set, a voiceimage transmission/reception unit and a mobile terminal unit. Theterminal-unit gateway 901-1 includes a network node unit 906-1 and aterminal-unit control section 914-1. The network node unit 906-1includes a unit control table 910-1. The terminal-unit control section914-1 includes a management telephone server 906-2, a table managementserver 906-3, a telephone management server 906-4, a telephone numberserver 906-5, a proxy mobile phone server 906-6 and a router 916-1. Theservers 906-2 to 906-5, the network node unit 906-1 and the router 916-1are connected together directly or indirectly through communicationlines. Similarly, the terminal-unit gateway 901-2 includes a networknode unit 907-1 and a terminal-unit control section 914-2. The networknode unit 907-1 includes a unit control table 910-2. The terminal-unitcontrol section 914-2 includes a proxy telephone server 907-2, a tablemanagement server 907-3, a telephone management server 907-4, atelephone number server 907-5, a proxy mobile phone server 907-6 and arouter 916-2.

[0578] Similarly, the terminal-unit gateway 901-3 includes a networknode unit 908-1 and a terminal-unit control section 914-3. The networknode unit 908-1 includes a unit control table 910-3. The terminal-unitcontrol section 914-3 includes a proxy telephone server 908-2, a tablemanagement server 908-3, a telephone management server 908-4, atelephone number server 908-5, a proxy mobile phone server 908-6 and arouter 916-3. Similarly, the terminal-unit gateway 901-4 includes anetwork node unit 909-1 and a terminal-unit control section 914-4. Thenetwork node unit 909-1 includes a unit control table 910-4. Theterminal-unit control section 914-4 includes a proxy telephone server909-2, a table management server 909-3, a telephone management server909-4, a telephone number server 909-5, a proxy mobile phone server909-6 and a router 916-4.

[0579] Numeral 995 is a superior telephone number server, numerals 990-1and 990-2 are users, numerals 991-1 and 991-2 are accepters, andnumerals 992-1 and 992-2 are user service servers. In contrast to thesuperior telephone number server 995, the telephone number servers 906-5to 909-5 are referred also to as lower-order telephone number servers.

[0580] In the invention, identification symbols are used also astelephone numbers and Internet host names (e.g. Host1. domain1. domain2.com.) in order to identify a telephone set or terminal unit. Thetelephone number server is inputted by an identification symbol toanswer a corresponding IP address and the related information. Therouters 916-1 to 916-4 are mutually connected by way of thecommunication lines and routers of the IP network 900. The communicationlines 912-1 to 912-6 are referred to as control communication lines ofthe IP network 900. The communication lines 913-1 to 913-6 are referredto as media communication lines of the IP network 900.

[0581] <<NNI and UNI>>

[0582] The transmission/reception procedure of an IP packet mutuallybetween the telephone management servers is referred to as an IP packettransmission/reception procedure in accordance with an NNI interface(Network-Network Interface). The NNI interface is standardized withinthe IP network 900. Meanwhile, the transmission/reception procedure ofan IP packet between the media router and the telephone managementserver is referred to as an IP packet transmission/reception procedurein accordance with a UNI (User-Network Interface). The UNI is referredto as a media router UNI. Similarly, the IP packettransmission/reception procedure between the radio base point and thetelephone management server is referred to as an IP packettransmission/reception procedure due to the UNI. The UNI is referred toas a radio base point UNI. In the case there is difference in the mediarouter or radio base point, the UNI can be in a different form. Thetelephone number server holds the UNI of a media router and a radio basepoint UNI.

[0583] The radio base points 902-1 to 902-4, the media routers 903-1 to903-4, the IP terminal units 905-10 to 905-17 have respective IPaddresses to be distinguished from the others, from respective of whichan IP packet can be forwarded to the proxy telephone server. For thispurpose, the IP address possessed by the media router, radio base point,telephone set or terminal unit is set in a communication record of aunit control table in a network node unit to be connected through acommunication line. The detailed method of practicing a communicationrecord is explained in another embodiment of the invention. In acommunication case 1 to 5, the NNI interface adopts a form applying aterminal-to-terminal communication connection method based on a commonchannel signaling system to the IP network.

[0584] <<Communication Case 1: Communication Between Fixed TelephoneSets>>

[0585]FIG. 109 is a diagram explaining the telephone communication fromthe mobile phone 905-1 to the fixed telephone set 905-4. The telephoneset 905-1 has a telephone number “TN1” while the telephone set 905-4 hasa telephone number “TN2”. Herein, the media router 903-1 includes anexternal IP address “EA1” while the media router 903-4 includes anexternal IP address “EA2”. An internal IP address “IA1” is provided to alogic terminal at an end of the communication line 917-1 while aninternal IP address “IA2” is provided to a logic terminal at an end ofthe communication line 917-2. The proxy telephone server 906-2 is givenwith an external IP address “EA81” and internal IP address “IA81” whilethe proxy telephone server 906-4 is with an internal IP address “IA91”.Similarly, the proxy telephone server 909-2 is given with an external IPaddress “EA82” and internal IP address “IA82” while the proxy telephoneserver 909-4 is with an internal IP address “IA92”. The telephone numberserver 906-5 is given with an internal address “IA96”.

[0586] <<Connection Phase>>

[0587] Taking a transceiver of the telephone set 905-1, a callconnection request is sent to the media router 903-1 (Step A01). Themedia router 903-1 sends back a call connection request acceptance (StepA02). Next, the media router 903-1 forms an IP packet 920 (FIG. 110)including an source IP address “EA1”, destination IP address “EA81”,source telephone number “TN1”, destination telephone number “TN2”. UDPport number “5006” used in telephone voice transmission and attendantinformation “Info1”, and sends it to the network node unit 906-1 (StepA04). The payload of the IP packet 920 is a UDP packet having its sourceand destination port numbers both given with “5060”. The attendantinformation “Info1” is a voice compression scheme kind or the like ofthe telephone set 905-1. The media router 903-4 at the other ofcommunication uses the attendant information “Info1”.

[0588] The network node unit 906-1 uses an internal IP address “IA1”given to the end of the communication line the external IP packet 920has inputted and a destination IP address “EA81” in the IP packet 920,to search through the unit control table 910-1 (FIG. 136). In thepresent case, the fist-lined record, i.e. record of “IA1, IA81, NA1,NA81, MA1, MA81, . . . ”, is applied to form an internal packet 921(FIG. 111). This is sent to a proxy telephone server 906-2 having aninternal IP address “IA81” (Step A05). Note that it is possible to adopta method of using the third item “NA1” and the fifth item “MA1” renderedzero in both values. This case is with an application method relaxing asource IP address condition in encapsulation as a first function of thecommunication record explained using the Equation (8).

[0589] In the case that the proxy telephone server 906-2 receives an IPpacket 921, it forms an IP packet 922 (FIG. 112) containing a payloadsection of an IP packet 921 and addresses “EA1, IA1, EA81, IA81” in thepayload section and sends it to the telephone management server 906-4(Step A06).

[0590] <<Regulation in the Number of Outgoing Calls on Each Line>>

[0591] The telephone management server 906-4 extracts a source IPaddress “EA1” from a received IP packet 922 and compares it with a callmanagement table 918-1 (FIG. 140). Concerning the record having an IPaddress “EA1”, this embodiment has the number of lines in service of“2”. The number of lines in service is increased by “1” to “3”, to becompared with the upper limit number of lines. Because the upper limitnumber of lines is “5”, the process proceeds to the next procedure. Whennot so, the subsequent process is suspended.

[0592] <<Circuit Identification Code Management>>

[0593] The telephone management server 906-4 reads out an IP packet 922(FIG. 112) and extracts a source telephone number “TN1” and destinationtelephone number “TN2”, to calculate a circuit identification code“CIC-2” for managing terminal-to-terminal communication from a set ofthese two telephone numbers according to a predetermined rule. Next, asa second lined record of a CIC management table 923 (FIG. 113), writtenare a circuit identification code “CIC-2”, source telephone number“TN1”, destination telephone number “TN2”, external IP address “EA1” andinternal IP address “IA1”, external IP address “EA81” and internal IPaddress “IA81”, internal IP address “IA91” in the telephone managementserver 906-4, procedure section “IAM” and write time (date and time)“St-2”.

[0594] Furthermore, the telephone management server 906-4 shows an IPpacket 924 (FIG. 114) containing a destination telephone number “TN2”and a query concerning the source telephone number “TN1” to thetelephone number server 906-5 (Step A07). The telephone number server906-5 answers the telephone management server 906-4 an IP packet 925(FIG. 115) containing an external IP address “EA2” of the media router903-4 the telephone set 905-4 is to connect and internal IP address“IA2” provided to the end of the communication line 917-2, an externalIP address “EA82” and internal IP address “IA82” of the proxy telephoneserver 909-2, an IP address “IA92” of the telephone management server909-4, and a UNI interface “UNI1” of the media router 903-1 and a UNIinterface “UNI2” of the media router 903-4 (Step A08). Incidentally, thetelephone number server 906-5 has acquired “UN12” by inquiring a UNIinterface of the media router 903-4 to the telephone number server 909-5via the superior telephone number server 995. The information exchangebetween the telephone number servers will be explained later.

[0595] The telephone management server 906-4 adds the IP addresses andUNI interface acquired from the telephone number server 906-5 to the CICmanagement table 923 (FIG. 113). This result is shown on thesecond-lined record in the CIC management table 926-1 (FIG. 116). Thetelephone management server 906-4, when exchanging the IP packet withthe media router 903-1 side, uses the UNI interface “UNI1” of within theCIC management table 926-1 to employ the following communicationprocedure (Steps A35, A45, A55, A73, A85, etc.).

[0596] <<Variation in UNI Acquisition>>

[0597] Concerning the media router 903-1 UNI, the media router 903-1 UNIcan be examined from an IP address of the proxy telephone server 906-2by the use of a UNI look-up 925-1 (FIG. 117). In Step A07, the telephonemanagement sever 906-2 makes an inquiry concerning only a destinationtelephone number “TN2”. In this method, the proxy telephone server 906-2is arranged to communicate with only a plurality of media routers havingthe same UNI. Incidentally, a plurality of proxy telephone servers canbe set up within the terminal-unit gateway 901-1 such that proxytelephone servers for handling the respective UNIs, such as proxytelephone servers 1 exclusive for media router 1 and proxy telephoneservers 2 exclusive for media router 2, are all previously provided tohandle the UNIs of individual media routers at the other end ofcommunication.

[0598] <<NNI>>

[0599] Next, the telephone management server 906-4 makes reference to IPaddress information of the CIC management table 926-1 (FIG. 116) toform, from the packet 922 (FIG. 112), an IP packet 927 (FIG. 118) forcall set request (IAM packet), and sends the IP packet 927 to thetelephone management server 909-4 (Step A21). Herein, the source IPaddress of the IP packet 927 is “IA91” of the telephone managementserver, and the destination IP address is “IA92” of the telephonemanagement server 909-4.

[0600] <<Regulation in the Number of Incoming Calls on Each Line>>

[0601] The telephone management server 909-4 extracts an address “EA2”of the destination media router 903-4 from a received IP packet 927(FIG. 118) and compares it with an incoming-call management table 918-2(FIG. 141). In this embodiment, the number of lines in service is “2”.The number of lines in service is increased by “1” to “3” and comparedwith the upper limit number of lines. Because the upper limit number oflines is “7”, the process proceeds to the next procedure. If not, nofurther progress.

[0602] <<Management of Circuit Identification Code>>

[0603] The telephone management server 909-4, receiving an IP packet927, extracts a circuit identification code “CIC-2” contained in itspayload, a procedure section “IAM”, a source telephone number “TN1”, adestination telephone number “TN2”, and an IP address (“EA1”, “IA1”,“EA81”, “IA81”, “IA91”, “EA2”, “IA2”, “EA82”, “IA82”, “IA92”, “UNI2”)and UNI kind, and writes and records them, as a record, to the CICmanagement table 926-2 (FIG. 119) of under the management of thetelephone management server 909-4. In the present case, these are arecord on the first line, and a write time “St-3” is also written. Fromthen on, the telephone management server 909-4, when exchanging an IPpacket with the media router 903-4, employs a communication procedure(Step A22, A33, A43, A53, A76, A83, etc.) based on the UNI interface“UNI2” of in the CIC management table 926-1.

[0604] The telephone management server 909-4, subsequently, forms an IPpacket 928 (FIG. 120) by using the information acquired from the IPpacket 927, and sends it to the proxy telephone server 909-2 (Step A22).The payload of the IP packet 928 includes a UDP segment and addressarea, wherein the UDP segment contains therein an IP address “EA1” of asource media router 903-1. The address area includes IP addresses “EA2,IA2, EA82, IA82”.

[0605] The proxy telephone server 909-2 uses the information acquiredfrom the IP packet 928 to form an IP packet 929 (FIG. 121), and sends itto the network node unit 909-1. The IP packet 929 having a sourceaddress “IA82” and destination address “IA2” reaches the network nodeunit 909-1 (step A23). The network node unit 909-1 uses the unit controltable 910-4 (FIG. 139) to decapsulate the received IP packet 929 therebyforming an IP packet 930 (FIG. 122) and thereafter sends the IP packet930 to the media router 903-4 (Step A24). The media router 903-4receives the IP packet 930 and confirms whether the containeddestination telephone number “TN2” is arrivable. In the case of allowedarrival, an incoming call notification is made to the telephone set905-4 (Step A25).

[0606] Furthermore, the media router 903-4 reads out and holds thecontent of the IP packet 930, i.e. source telephone number “TN1”,destination telephone number “TN2”, source IP address “EA1”, source UDPport number “5006” and attendant information “Info1”. The media router903-4 forms an IP packet containing a source telephone number “TN1”,destination telephone number “TN2” and arrivability in order to notifythe arrivability at the telephone set 905-4 (partition of arrivabilityor nonarrivability), and notifies it to the telephone management server909-4 (Steps A31, A32, A33). The telephone management server 909-4receives the IP packet the media router 903-4 has formed and extractsthe information of source telephone number “TN1”, destination telephonenumber “TN2” and arrivability. Then, a circuit identification code“CIC-2” is calculated from the two telephone numbers, and an IP packet931 (FIG. 123) (ACM packet) containing a circuit identification code“CIC-2” and arrival-allowing/not-allowing information is formed and sentto the telephone management server 906-4 (Step A34). The telephonemanagement server 906-4 extracts the circuit identification code “CIC-2”and procedure partition “ACM” from the received IP packet 931 andexamines the CIC management table 926-1 (FIG. 116) held by the telephonemanagement server 906-4 to find a record having a circuit identificationcode “CIC-2” thus rewriting a record procedure partition column into aprocedure partition “ACM”. Incidentally, the telephone management server906-4 is allowed to generate an IP packet representative of ACM-packetreception (including arrivability information) and inform the mediarouter 903-1 of it (Steps A35 to A37, option).

[0607] Meanwhile, following the Step A25, when the telephone set 905-4reports an in-calling to the media router 903-4 (Step A40), the mediarouter 903-4 forms an IP packet 932 (FIG. 124) containing a sourcetelephone number “TN1”, destination telephone number “TN2”, UDP portnumber “5008” for use in voice communication by the telephone set 905-4,and attendant information “Info1”, and forwards it to the network nodeunit 909-1 (Step A41). In the network node unit 909-1, the first-linedcommunication record “IA2, IA82, NA2, NA82, MA2, MA82, “of a unitcontrol table 910-4 (FIG. 139) is used to encapsulate the IP packet 932into an IP packet 932-1 (FIG. 125) (Step A42). This turns into an IPpacket 932-2 (FIG. 126) in the proxy telephone server 909-2 andnotification is made to the telephone management server 909-4 (StepA43).

[0608] The telephone management server 909-4 extracts the sourcetelephone number “TN1” and destination telephone number “TN2” from theIP packet 932-2 and calculates a circuit identification code “CIC-2”from the two telephone numbers, to form an IP packet 933 (FIG. 127, CPGpacket) representative of an in-calling and send it to the telephonemanagement server 906-4 (Step A44). The IP packet 933 contains the UDPport number “5008” and attendant information “Info2” acquired from theIP packet 932-2. The telephone management server 906-4 extracts thecircuit identification code “CIC-2”, procedure partition “CPG”, UDP portnumber “5008” and attendant information “Info2” from the IP packet 933and rewrites a procedure partition of a record having a circuitidentification code “CIC-2” of the CIC management table 926-1 (FIG. 116)to “CPG”. From the CIC management table 926-1, an IP address “EA1, IA1,EA81, IA81”, source telephone number “TN1” and destination telephonenumber “TN2” is readout. Using the read-out information, an IP packet933-1 (FIG. 128) is formed and sent to the proxy telephone server 906-2(Step A45).

[0609] The proxy telephone server 906-2 forms an IP packet 933-2 (FIG.129) and sends it to the network node unit 906-1 (Step A46). The networknode unit 906-1 decapsulates the IP packet 933-2 to form an IP packet933-3 (FIG. 130) and sends it to the media router 903-1 (Step A47). Themedia router 903-1 reads a telephone numbers “TN1” and “TN2”, IP address“EA2”, UDP port number “5008” and attendant information “Info2” out ofthe IP packet 933-3, and holds it. The media router 903-1 forwards anin-calling signal to the telephone set 905-1 (Step A48).

[0610] Next, in the case that the telephone set 905-4 obtains an answerto a call having continued after the Step A40, it sends an answer on adestination telephone set to the media router 903-4 (Step A50). Themedia router 903-4 sends an IP packet containing a source telephonenumber “TN1” and destination telephone number “TN2” to the telephonemanagement server 909-4 in order to notify the answer (Steps A51 toA53). The IP packet informing the answer has a form similar to the formof the IP packet in Steps A41 to A43. Incidentally, the media router903-4 can send an answer confirmation on the answer in the step A50 backto the telephone set 905-4 (Step A60, option).

[0611] The telephone management server 909-4 extracts the sourcetelephone number “TN1” and destination telephone number “TN2” out of thereceived IP packet and calculates a circuit identification code “CIC-2”from the two telephone numbers, to form an IP packet 934 (FIG. 131) (ANMpacket) including at least a circuit identification code “CIC-2”notifying a response and send it to the telephone management server906-4 (Step A54). The telephone management server 906-4 extracts thecircuit identification code “CIC-2” and procedure partition “ANM” out ofthe received IP packet 934, and examines a CIC management table 926-1(FIG. 116) held by the telephone management server 906-4 to find arecord of a circuit identification code “CIC-2”, thereby rewriting aprocedure partition column of the record into a procedure partition“ANM”.

[0612] Next, the telephone management server 906-4 notifies the mediarouter 903-1 of an ANM packet reception, i.e. a response by thetelephone set 905-4 to the call (Steps A55, A56, A57). The media router903-1 sends an answer signal to the telephone set 905-1 (Step A58). Thetelephone set 905-1 can send back an answer confirmation signal to theanswer signal (Step A59, option). In the Steps A45 to A47, notificationof an in-calling is made, and in the Steps A55 to A57, a response of adestination telephone set is notified.

[0613] <<Setting of Communication Record>>

[0614] The telephone management server 909-4, after the Step A54,extracts an IP address “EA2”, “EA1”, “IA2”, “IA1” from a record having acircuit identification code “CIC-2” from a CIC management table 926-2(FIG. 119), and sends it to the table management server 909-3 (StepA64). The table management server 909-3 sets a third-lined record “IA2,IA1, EA2, EA1, MK2, MK1, . . . ” of a unit control table 910-4 (FIG.139) of within the network node unit 909-1 (Step A65). Herein,MK1=255.255.255.255, MK2=255.255.255.255. Similarly, The telephonemanagement server 906-4, after the step A55, extracts an IP address“EA1”, “EA2”, “IA1”, “IA2” from a record having a circuit identificationcode “CIC-2” from a CIC management table 926-1 (FIG. 116), and sends itto the table management server 906-3 (Step A66). The table managementserver 906-3 sets it as a second-lined record “IA1, IA2, EA1, EA2, MK1,MK2, . . . ” of a unit control table 910-1 (FIG. 139) of within thenetwork node unit 906-1 (Step A67). Each sub-table (filter controlrecords, etc.) is set in the Step A64 and A66.

[0615] <<Communication Phase>>

[0616] The telephone communication between the telephone set 905-1 andthe telephone set 905-4 has steps similar to those explained in theother embodiment. This uses the second-lined communication record (“IA1,IA2, EA1, EA2, MK1, MK2, . . . ”) set in the connection phase in theunit control table 910-1 (FIG. 136) and the third-lined communicationrecord (“IA2, IA1, EA2, EA1, MK2, MK1, . . . ”) in the unit controltable 910-4 (FIG. 139). The voice by the telephone set 905-1 isdigitalized and placed onto a payload of an IP packet 935 (FIG. 132).Herein, the destination address and UDP port number acquired in theabove is used. Namely, the source address is an IP address “EA1” of themedia router 903-1, and the destination address is an IP address “EA2”of a media router 903-4 to which destination telephone set 905-4 is toconnect. The source UDP port number uses “5006”, and destination UDPport number uses “5008”. An analog voice is sent from the telephone set905-1 (Step A68-1). In the media router 903-1, the voice is digitalizedinto a voice IP packet 935 to be sent to the network node unit 906-1(Step A68-2). Herein, this is encapsulated into an IP packet 936 (FIG.133), reaching the network node unit 909-1 via an IP communication line,i.e. by way of the routers 911-4 to 911-6 of FIG. 108 (Step A68-3).Herein, this is decapsulated to reach the media router 903-4 (StepA68-4) and returned into an analog voice, reaching the telephone set905-4 (Step A68-5). The analog voice sent from the telephone set 905-4is digitalized and contained in an IP packet, thus being sent in areverse direction to the foregoing (Steps A69-1 to A69-5).

[0617] Summarizing the IP encapsulation in the above, an external packetis inputted at a logic terminal on the communication line of outside theIP network 900. By defining three sets of the inputted source-sidedlogic terminal identifier information, external-IP-packet sourceexternal IP address and destination external IP address, atransfer-destination internal address is defined for an internal packetunder the control of the communication record of the unit control table.Thus, the internal packet is transferred within the communicationnetwork. This can be reworded that, between the source-sided anddestination-sided network node units, an internal communication line forinternal packet transfer is defined. The internal packet is transferredwithin the communication network, and restored into an external packetin the destination-sided network node unit. Note that it is possible toadopt an internal packet formed without using a source external IPaddress of within the external packet, by the use of two sets of theinput source-sided logic terminal identifier information and thedestination external IP address of within the external packet.

[0618] <<Release Phase>>

[0619] When the utilizer of the telephone set 905-1 notifies a releasefrom telephone communication (Step A70 in FIG. 109), it is notified tothe telephone management server 906-4 by way of the media router 903-1,network node unit 906-1 and proxy telephone server 906-2 (Steps A70 toA73). The telephone management server 906-4 writes an end time “Ed-1”into an end time column having a record of circuit identification code“CIC-2” in the CIC management table 926-1 (FIG. 116). Next, a release IPpacket 937 (FIG. 134) (REL packet) is formed and notified to thetelephone management server 909-4 (Step A74). Furthermore, the telephonemanagement server 906-4 notifies a release instruction to the mediarouter 903-1 by way of the proxy telephone server 906-2 and network nodeunit 906-1 (Step A85 to A87). The media router 903-1, receiving therelease notification in the step A70, can send a disconnect confirmationto the telephone set 905-1 (Step A70-1, option).

[0620] The telephone management server 909-4, receiving the IP packet937 (Step A74), writes an end time “Ed-2” in an end time column of arecord having a circuit identification code “CIC-2” in the CICmanagement table 926-2 (FIG. 119), and forms a release completion IPpacket 938 (FIG. 135) (RLC packet) and sends it back to the telephonemanagement server 906-4 in order to report a reception of the release IPpacket 937 (Step A84). Furthermore, the telephone management server909-4 forwards a telephone-communication release instruction to themedia router 903-4 by way of the proxy telephone server 909-2 andnetwork node unit 909-1 (Step A76 to A78).

[0621] The media router 903-4 notifies a disconnect instruction for therelease instruction to the telephone set 905-4 (Step A79) notifying arelease report for the release instruction to the telephone managementserver 909-4 via the proxy telephone server (Step A81 to A83). Thetelephone set 905-4 can send a disconnect-instruction confirmationresponsive to the disconnect instruction sent from the media router903-4 (Step A80, option). Furthermore, the media router 903-4 can send aconfirmation further to the disconnect-instruction confirmation (StepA80-1, option).

[0622] <<Deletion of Communication Record>>

[0623] After the Step A74, the telephone management server 906-4 sendsthe circuit identification code “CIC-2” of within the IP packet 937 tothe table management server 906-3 (Step A96). The table managementserver 906-3 deletes the relevant communication record, i.e. in thepresent case, the second-lined record “IA1, IA2, EA1, EA2, MK1, MK2” ofthe unit control table 910-1 (FIG. 136) (Step A97). After the Step A74,the telephone management server 909-4 sends a circuit identificationcode “CIC-2” of within the received release IP packet 937 to the tablemanagement server 909-3 (Step A98). The table management server 909-3deletes the relevant communication record, i.e. in the present case, thethird-lined record “IA2, IA1, EA2, EA1, MK2, MK1” of the unit controltable 910-4 (FIG. 139) (Step A99).

[0624] <<Post-Process to Regulation in the Number of Outgoing andIncoming Calls>>

[0625] After the Step A74, the telephone management server 906-4subtracts “1” from the number of lines in service corresponding to anaddress “EA1” written in an outgoing-call management table 918-1 (FIG.140). Similarly, after the Step A84, the telephone management server909-4 subtracts “1” from the number of lines in service corresponding toan address “EA2” written in an incoming-call management table 918-2(FIG. 141).

[0626] <<Collection of Voice-Communication Information>>

[0627] In the communication case 1 explained above, the managementcontrol server 915 (FIG. 108) can exchange information with thetelephone management servers 906-4 and 909-4 (Steps A100, A101 in FIG.142) to obtain a telephone communication record described in the CICmanagement tables 926-1 (FIG. 116) and 926-2 (FIG. 119), e.g. sourcetelephone number, destination telephone number, start time, end time,etc., thereby offering it for the purpose of imposing telephonecommunication fee. Meanwhile, the management control server 915 canexchange information with the table management servers 906-3 and 909-3(Steps A102, A103) to obtain the information described in communicationrecord in the unit control tables 910-1 and 910-4 (FIG. 108), therebyoffering it for the purpose of IP network 900 operation or imposingtelephone communication fee.

[0628] <<Communication Record Setting Method>>

[0629] The communication record for use in IP packet transmission andreception between the media router 903-1 and the proxy telephone server906-2 (communication record used for terminal-to-terminal communicationconnection control), e.g. the first-lined communication record “IA1,IA81, NA1, NA81, MA1, MA81, . . . ” of the unit control table 910-1(FIG. 136), has been previously set prior to carrying outterminal-to-terminal communication. The communication record for use inmedia transmission and reception between the terminal units but not usedin terminal-to-terminal communication connection control, such as thesecond-lined communication record “IA1, IA2, EA1, EA2, MK1, MK2, . . . ”of the unit control table 910-1, is dynamically set or deleted throughthe table management server as in the foregoing explanation.Incidentally, the communication record to be previously set and thecommunication record to be dynamically set are set up on anther domainof a memory of within the network node unit, thus simplifying memorymounting. This is true for the communication cases 2 to 6 referredlater.

[0630] <<Telephone Number Registration of Fixed Telephone Set>>

[0631] Explanation is made on a registration method of a fixed telephoneset and communication record setting of a capsule control table in thecommunication case 1, with reference to FIGS. 108 and 208.

[0632] The user 990-1 of a fixed telephone set 905-1 defines an externalIP address “EA1” and telephone number “TN1” according to an operationrule of the IP network 900 or by consultation with the common carrier,and offers an application for utilizing the fixed telephone set 905-1,including at least a user name and payment of communication fee, to atelephone accepter 991-1 (Step P1 in FIG. 208). The telephone accepter991-1 examines an identification sign N903-1 of the media router thefixed telephone 905-1 is to connect, an identification number N906-1 ofthe network node unit 906-1 and an identification sign N917-1 of thecommunication line 917-1 by using an acceptance business data held bythe telephone accepter 991-1, and notifies the user 990-1 of theidentifiable information on the media router 903-1 the fixed telephone905-1 is to connect. User 990-1 sets the external IP address “EA1” ontothe fixed telephone 905-1.

[0633] Incidentally, in a case that an external IP address “EA1” is setinto the media router 903-1, the telephone accepter 991-1 notifies anexternal IP address “EA1” to the user 990-1. The user 990-1 sets atelephone number “TN1” to the fixed telephone set 905-1. By the aboveprocedure, the telephone accepter 991-1 acquires the acceptanceinformation including, at least, an external IP address “EA1”, atelephone number “TN1”, a user name, communication-fee payment, anidentification sign N906-1 of the network node unit 906-1, anidentification sign N903-1 of the media router and an identificationsign N917-1 of the communication line 917-1.

[0634] Next, the accepter 991-1 notifies the acceptance information to auser service server 992-1 (Step P2). The user service server 992-1 usesthe identification sign N906-1 of the network node unit and theidentification sign N917-1 of the communication line, to fix an internalIP address “IA1” and adds it to the acceptance information according tothe internal address-providing rule data held in the user service server992-1, thus holding the acceptance information including the internaladdress “IA1in its database (Step P3). Next, the user server 992-1notifies the telephone management server 906-4 of, at least, an externalIP address “EA1”, internal IP address “IA1”, telephone number “TN1”,identification sign N906-1 of the network node unit 906-1,identification sign N903-1 of a media router 903-1 related to thetelephone number “TN1”, identification sign N917-1 of the communicationline 917-1, UNI of the media router 903-1, external address “EA81” andinternal address “IA81” of the proxy telephone server 906-2 to exchangeinformation with the media router 903-1, and internal address “IA91” ofthe telephone management server 906-4 to exchange information with theproxy telephone server 906-2 (Step P4). The telephone management server906-4 notifies the telephone number server 906-5 of, at least, anexternal IP address “EA1”, internal IP address “IA1” and telephonenumber “TN1” of among the acquired acceptance information (Step P5). Thetelephone number server 906-5 holds therein, of among the acquiredinformation, at least an external IP address “EA1”, internal IP address“IA1” and telephone number “TN1”, according to a data storage form of adomain name server defined, for example, under RFC1996 or RFC1035 (StepP6). The telephone number server 906-5 notifies the superior server 995of holding a telephone number “TN1” together with an identification signN906-1 of the telephone server 906-5 and IP address (Step P7). Thetelephone number server 995 holds therein at least a set of anidentification sign N906-1 of the telephone number server 906-5, the IPaddress and the telephone number “TN1” (Step P8). The superior telephoneserver 995 holds an identification sign and IP address of anothertelephone number server holding a telephone number “TN-x”.

[0635] <<Variation>>

[0636] The Steps P5 to P8 (FIG. 208) can be changed to Steps P5 x to P8x in the following. The telephone management server 906-4 notifies thetelephone number server 906-5 (Step P6 x) of at least an external IPaddress “EA1”, internal IP address “IA1” and telephone number “TN1” ofamong the acquired acceptance information through the superior telephonenumber server 995 (Step P5 x). The telephone number server 906-5 holdstherein the received external IP address “EA1”, internal IP address“IA1” and telephone number “TN1”. Herein, the superior telephone numberserver 995 holds an identification symbol and IP address of the othertelephone number server 906-5 holding the telephone number “TN-x”.Meanwhile, the telephone number server 906-5 can report a result (StepP7 x, Step P8 x).

[0637] Furthermore, the user service server 991-1 can request thesuperior telephone number server 995 through the telephone managementserver 906-4 or directly without through the same, to rewrite or deletethe content of the superior telephone number server 995. User serviceserver 991-1 can hold the multicast reception authentication informationcan be held (option).

[0638] <<Information Exchange Function Between Telephone NumberServers>>

[0639]FIG. 209 shows that mutual information exchange can be madebetween the superior telephone number server 995 within the IP network900 and the inferior telephone number servers 906-5, 907-5, 908-5 and909-5. Furthermore, the inferior telephone number servers 906-5, 907-5,908-5 and 909-5 can perform information exchange through the superiortelephone number server 995. For example, when the telephone numberserver 907-5 inquires the telephone number server 995 of an external IPaddress and internal IP address accompanied by the telephone number “N1”(Step P20 in FIG. 210), the telephone number server 995 inquires thetelephone management server 906-5 holding therein an IP addressaccompanied by the telephone number “TN1” (Step P21) to acquire anexternal IP address “EA1” and internal IP address “IA1” (Step P22).Next, the telephone number server 995 notifies the telephone numberserver 907-5 of the obtained external IP address “EA1” and internal IPaddress “IA1” accompanied by the telephone number “TN1” (Step P23). Thesuperior telephone number server 995 is characterized by holding anidentification symbol of an inferior telephone number server holding atelephone number “TN-x” and identification symbol, IP address andmulticast reception authentication information (option), and furtherholding terminal-unit authentication information in concerned with amobile phone as described later.

[0640] <<Communication Case 2: Communication Between Mobile Phones>>

[0641]FIGS. 143 and 144 are a diagram explaining the telephonecommunication of from the mobile phone 905-6 to the mobile phone 905-8.The telephone set 905-6 has a telephone number “TN3”, and the telephoneset 905-8 has a telephone number “TN4”. Herein, a radio base point 902-3includes an external IP address “EB1”, a radio base point 902-4 includesan external IP address “EB2”, a communication line 917-3, at an end, isprovided with an internal IP address “IB1”, and a communication line917-4, at an end, is provided with an internal IP address “IB2”. Theproxy mobile phone server 908-6 is provided with an external IP address“EB81” and internal IP address “IB81”. The proxy telephone server 908-4is provided with an internal IP address “IB91”. The telephone numberserver 908-5 is given the internal IP address “IB96”, the proxy mobilephone server 909-6 is given the internal IP address “IB82”, thetelephone management server 909-4 is given the internal IP address“IA92” respectively. The external addresses of the telephone numberservers 906-6 to 906-6 to 909-5 are all “EA81”, and the externaladdresses of the proxy mobile phone servers 906-6 to 909-6 are all“EB81”.

[0642] <<Connection Phase>>

[0643] In the case that a call connection request is forwarded from thetelephone set 905-6 via a radio communication line 917-5, a radiochannel connection request signal is conveyed to the radio base point902-3 (Step B01). The radio base point 902-3 sends a call connectionrequest acceptance for the call connection request to the telephone set905-6 (Step B02). Next, from the telephone set 905-6, a call set requestincluding a source telephone number “TN3” and destination telephonenumber “TN4” is forwarded to the radio base point 902-3 (Step B03). Theradio base point 902-3 forms an IP packet 920B (FIG. 129) containing acall set request comprising an source IP address “EB1”, destination IPaddress “EB81”, source telephone number “TN3”, destination telephonenumber “TN4”, port number “5006” used in telephone voice transmission bythe radio base point 902-3 and attendant information “Info3” on thebasis of a content of the received call set request, and sends it to thenetwork node unit 908-1 (Step B04).

[0644] The network node unit 908-1 applies a first-lined record of theunit control table 910-3 (FIG. 138) to encapsulate the IP packet 920Band form an internal packet 921B (FIG. 146), thereby sending it to theproxy mobile phone server 908-6 (Step B05). The proxy mobile phoneserver 908-6 forms an IP packet 922B (FIG. 147) on the basis of the IPpacket 921B and sends it to the telephone management server 908-4 (StepB06).

[0645] <<Circuit Identification Code Management>>

[0646] Next, the telephone management server 908-4 uses a content of theIP packet 922B (FIG. 147) to calculate a circuit identification code“CIC-3” from the set of a source telephone number “TN3” and destinationtelephone number “TN4”, thus forming a CIC management table 923B (FIG.148). Furthermore, the telephone management server 908-4 shows an IPpacket 924B (FIG. 149) containing a query concerning the destinationtelephone number “TN4” and source telephone number “TN3” to thetelephone number server 908-5 (Step B07) and receives an IP packet 925B(FIG. 150) containing an answer to the query (Step B08). The telephonemanagement server 908-4 adds the CIC management table 923B (FIG. 148)with the acquired addresses and “UN13” of an UNI interface of the radiobase point 902-3. The result of this is shown in a first-lined record ofthe CIC management table 926-1B (FIG. 151). The telephone managementserver 908-4, from now on, uses a communication procedure (Steps B09,B16, B17, B35, B45, B55, B73, B85, etc.) on the basis of the UNIinterface “UNI3” in the CIC management table 926-1B.

[0647] Next, the telephone management server 908-4 forms an IP packet939B09 (FIG. 152) containing a call set acceptance, authenticationrequest, telephone numbers “TN3” and “TN4” and forwards it to the proxymobile phone server 908-6 (Step B09). The proxy mobile phone server908-6 forms an IP packet 939B10 (FIG. 153) and sends it to the networknode unit 908-1 (Step B10). The network node unit 908-1 decapsulates theIP packet 939B10 to form an IP packet 939B11 (FIG. 154), and thereaftersends the IP packet 939B11 to the radio base point 902-3 (Step B11). Thebase point 902-3 notifies the telephone set 905-6 of a call setacceptance and authentication request on the basis of the informationcontained in the IP packet 939B11 received via a radio communicationpath 917-5 (Step B12).

[0648] The telephone set 905-6 forwards an authentication answerrepresentative of terminal-unit correctness (password or the like) tothe radio base point 902-3 via the radio communication path 917-5 (StepB13). The radio base point 902-3 forms an IP packet 939B14 (FIG. 155)containing an authentication answer and forwards it to the network nodeunit 908-1 (Step B14). A new IP packet 939B15 (FIG. 156) containing anauthentication answer obtained by encapsulation in the network node unit908-1, reaches the proxy mobile phone server 908-6 (Step B15). Next, anew IP packet 939B16 (FIG. 157) containing an authentication answerreaches the telephone management server 908-4 (Step B16).

[0649] The telephone management server 908-4 forwards an IP packetcontaining a terminal-unit authentication properness/improperness forcommunication channel set instruction to the proxy mobile phone server908-6 (Step B17). The new IP packet containing a terminal-unitauthentication properness/improperness reaches the network node unit908-1 and decapsulated (Step B18), reaching the base point 902-3 (StepB19). The radio base point 902-3 notifies the IP-packet's terminal-unitauthentication properness/improperness to the telephone set 9055-6 viathe radio communication path 917-5 (Step B20). The IP packet transferredin the Step B17 to B19 has a form similar in address storage form or thelike to the IP packet transferred in the Steps B09 to B11. Next, thetelephone management server 908-4 makes reference to the IP addressinformation of the CIC management table 926-1B (FIG. 151) and to thepacket 922B (FIG. 147), to form an IP packet 927B (FIG. 158) (IAMpacket) for a call set request and send the IP packet 927B to thetelephone management server 909-4 (Step B21).

[0650] <<Circuit Identification Code Management>>

[0651] The telephone management server 909-4, receiving the IP packet927B, extracts a circuit identification code “CIC-3”, a procedurepartition “IAM”, a source telephone number “TN3”, a destinationtelephone number “TN4”, IP addresses in plurality and a UNI interface“UN14” contained in a payload thereof, and writes and records them as arecord to the CIC management table 926-2B (FIG. 159). The write time“St-4” of the same is also written.

[0652] Next, the telephone management server 909-4 uses the received IPpacket 927B to form an IP packet 928B (FIG. 160) containing a call setrequest, and forwards the IP packet 928B to the proxy mobile phoneserver 909-6 (Step B22). The proxy mobile phone server 909-6 forms an IPpacket 929B (FIG. 161) and sends it to the network node unit 909-1 (StepB23). The network node unit 909-1 decapsulates the received IP packet929B to form an IP packet 930B (FIG. 162) and thereafter sends the IPpacket 930B to the radio base point 902-4 (Step B24). The base point902-4 temporarily notifies the telephone set 905-8 of an incoming callvia the radio communication path 917-6, on the basis of the received IPpacket 930B (Step B25).

[0653] The telephone set 905-8, when receiving the call temporarynotification (Step B25), reports a state of the radio communication path917-6 (noise, voice quality, etc.) to the radio base point 902-4 (StepB26) and subsequently forwards the information signifying aterminal-unit correctness (password or the like) to the radio base point902-4 via the radio communication path 917-6 (Step B27 a). The radiobase point 902-4 forms an IP packet 939B27B (FIG. 163) containing theinformation signifying a terminal-unit correctness and forwards it tothe network node unit 909-1 (Step B27 b). The IP packet 939B27B isencapsulated into an IP packet 939B27C (FIG. 164) in the network nodeunit 909-1. The IP packet 939B27C reaches the proxy mobile phone server909-6 (Step B27 c) and turns into an IP packet 939B27D (FIG. 165) thusreaching the telephone management server 909-4 (Step B27 b).

[0654] The telephone management server 909-4 forwards an IP packet93928A (FIG. 166) containing a terminal-unit authenticationproperness/improperness for communication channel set instruction to theproxy mobile phone server 909-6 (Step B28 a). This, in the proxy mobilephone server 909-6, turns into an IP packet 939B28B (FIG. 167) and theIP packet 939B28B reaches the network node unit 909-1 (Step B28 b). TheIP packet 939B28B is decapsulated into an IP packet 939B28C (FIG. 168)thus reaching the base point 902-4 (Step B28 c). The radio base point902-4 notifies the information including an IP-packet's terminal-unitauthentication properness/improperness to the telephone set 905-8 viathe radio communication path 917-6 (Step B28 d). Next, the radio basepoint 902-4 examines whether the destination telephone number “TN4” isarrivable, and notifies the telephone set 905-8 of an incoming call(Step B30). The radio base point 902-4 holds a content of the IP packet930B, i.e. telephone numbers “TN3” and “TN4”, address “EB1”, port number“5006” and “Info3”. Next, the radio base point 902-4 forms an IP packetcontaining telephone numbers “TN3” and “TN4” and arrivalallowing/not-allowing report information and notifies it to thetelephone management server 909-4 (Steps B31 to B33). The telephonemanagement server 909-4 extracts a source telephone number “TN3”,destination telephone number “TN4” and arrival allowing/not-allowingreport information from the received IP packet. A circuit identificationcode “CIC-3” is calculated from the two telephone numbers, to form an IPpacket 931B (FIG. 169) containing a circuit identification code “CIC-3”and information on the arrivability at the telephone set 905-8 (FIG.169) (ACM packet) and sends it to the telephone management server 908-4(Step B34). The telephone management server 908-4 extracts a circuitidentification code “CIC-3” and procedure partition “ACM” from thereceived IP packet 931B and examines the CIC management table 926-1B(FIG. 151) to find a record having a circuit identification code “CIC-3”thereby rewriting the procedure partition to “ACM”. Next, the telephonemanagement server 908-4 can generate an IP packet representative of anACM packet reception, notifying it to the radio base point 902-3 (StepsB35 to B37, option).

[0655] The radio base point 902-4, receiving an in-calling from thetelephone set 905-8 (Step B40), forms a IP packet 932B (FIG. 170)containing a source telephone number “TN3” and destination telephonenumber “TN4”, port number “5008” used in voice transmission by thetelephone set 905-8, and attendant information “Info4” and sends it tothe network node unit 909-1 (Step B41). The network node unit 909-1encapsulates the IP packet 932B to form an IP packet 932-1B (FIG. 171),and sends it to the proxy mobile phone server 909-6 (Step B42). Theproxy mobile phone server 909-6 forms an IP packet 932-2B (FIG. 172) andsends it to the telephone management server 909-4 (Step B43). Thetelephone management server 909-4 extracts the telephone numbers “TN3”and “TN4” from the received IP packet 932-2B to calculate a circuitidentification code “CIC-3” from the two telephone numbers, to form anIP packet 933B (FIG. 173) (CPG packet) representative of an in-callingand send it to the telephone management server 908-4 (Step B44). Thetelephone management server 908-4 extracts the circuit identificationcode “CIC-3”, procedure partition “CPG”, UDP port number “5008” andattendant information “Info4” from the received IP packet 933B andrewrites a procedure partition of a record of circuit identificationcode “CIC-3” of the CIC management table 926-1B (FIG. 151) to “CPG”. IPaddress “EB1, IB1, EB81, IB81”, source telephone number “TN3” anddestination telephone number “TN4” are read out. Using the acquiredinformation, an IP packet 933-1B (FIG. 174) is formed and sent to theproxy mobile phone server 908-6 (Step B45).

[0656] The proxy telephone server 908-2 uses the received IP packet933-1B to form an IP packet 933-2B (FIG. 175) and sends it to thenetwork node unit 908-1 (Step B46). The network node unit 908-1decapsulates the received IP packet 933-2B to form an IP packet 933-3B(FIG. 176) and sends it to the radio base point 902-3 (Step B47). Theradio base point 902-3 reads out and holds telephone numbers “TN3” and“TN4”, IP address “EB2”, port number “5008” and attendant information“Info4” contained in the IP packet 933-3B. The radio base point 902-3notifies the telephone set 905-6 of an in-calling of the destinationtelephone 905-8 (Step B48).

[0657] Next, the telephone set 905-8 responds to a call (Step B50). Theradio base station 902-4 sends an IP packet containing a sourcetelephone number “TN3” and destination telephone number “TN4” to thetelephone management server 909-4 in order to notify the answer (StepsB51 to B53). The telephone management server 909-4 extracts the sourcetelephone number “TN3” and destination telephone number “TN4” from thereceived IP packet to calculate a circuit identification code “CIC3”from the two telephone numbers, and forms an IP packet 934B (FIG. 177)(ANM packet) containing, at least, a circuit identification code “CIC-3”notifying the answer, thus sending it to the telephone management server908-4 (Step B54). Note that the telephone management server 909-4 cansend a response confirmation back to the radio base point (Steps B60-1to 60-4, option).

[0658] The telephone management server 908-4 extracts a circuitidentification code “CIC-3” and procedure partition “ANM” from thereceived IP packet 934B and examines the CIC management table 926-1B(FIG. 151) processed by the telephone management server 908-4 to find arecord having a circuit identification code “CIC-3” thereby rewritingthe procedure partition column to “ANM”. Next, the telephone managementserver 908-4 notifies the radio base point 902-3 of a call response bythe telephone set 905-8 by way of the proxy mobile phone server 908-6and network node unit 908-1 (Steps B55 to B57). The radio base point902-3 forwards a call signal to the telephone set 905-6 (Step B58). Thetelephone set 905-6 can send back a confirmation of response (Step B59,option).

[0659] <<Communication Record Setting>>

[0660] The telephone management server 909-4 makes reference to the CICmanagement table 926-2B (FIG. 159) to acquire communication-recordchange information, and sends it to the table management server 909-3(Step B64). The table management server 909-3 sets it as a fourth-linedrecord “IB2, IB1, EB2, EB1, MK5, MK6, . . . ” of a unit control table910-4 (FIG. 139) in the network node unit 909-1 (Step B65). Herein, themask information MK5 and MK6 is rendered “255.255.255.255”. Similarly,the telephone management server 908-4 makes reference to the CICmanagement table 926-1B (FIG. 151) to acquire communication-recordchange information, and sends it to the table management server 908-3(Step B66). The table management server 908-3 sets it as a third-linedrecord “IB1, IB2, EB1, EB2, MK6, MK5, . . . ” of a unit control table910-3 (FIG. 138) in the network node unit 908-1 (Step B67).

[0661] <<Communication Phase>>

[0662] The telephone communication between the telephone set 905-6 andthe telephone set 905-8 has steps similar to those explained in theother embodiment, using a third-lined record “IB1, IB2, EB1, EB2, MK6,MK5, . . . ” of the unit control table 910-3 and a fourth-lined record“IB2, IB1, EB2, EB1, MK5, MK6, . . . ” of the unit control table 910-4.The voice on the telephone set 905-6 is digitalized and placed onto apayload of an IP packet 935B (FIG. 178). Herein, used is a destinationaddress and UDP port number obtained in the connection phase. The voiceis transferred in the form of a radio communication wave over the radiocommunication path 917-5 from the telephone set 905-6 (Step B68-1). Inthe radio base point 902-3, the voice is digitalized into a voice IPpacket 935B (FIG. 178). This is sent to the network node unit 908-1(Step B68-2) where it is encapsulated into an IP packet 936B (FIG. 179).Furthermore, this reaches the network node unit 909-1 via the router911-6 (FIG. 108) and the communication line 913-5 (Step B683), anddecapsulated in the network node unit 909-1 thus reaching the radio basepoint 902-4 (Step B68-4). The voice restored in an analog voice isconveyed in the form of a radio communication wave over the radiocommunication path 917-6 to reach the telephone set 905-8 (Step B68-5).The analog voice sent from the telephone set 905-8 is digitalized andstored in an IP packet, thus being sent in a reverse direction (StepB69-1 to B69-5). In the Steps B68-1, B68-5, B69-1, B69-5, it is possiblethat digitalized voices are transferred via wireless paths 917-5, 917-6.

[0663] <<Release Phase>>

[0664] In the case that the utilizer of telephone set 905-6 notifies arelease of telephone communication (Step B70 in FIG. 144), it isnotified to the telephone management server 908-4 by way of the radiobase point 902-3, the network node unit 908-1 and proxy mobile phoneserver 908-6 (Steps B70 to B73). The telephone management server 908-4writes an end time “Ed-1” into an end time column of a record having acircuit identification code “CIC-3” in the CIC management table 926-1B(FIG. 151). Next, a release IP packet 937B (FIG. 180, REL packet) isformed for notification to the telephone management server 909-4 (StepB74). The telephone management server 909-4 notifies atelephone-communication release instruction to the radio base point902-4 via the proxy mobile phone server 909-6 (Steps B76 to B78).Furthermore, the telephone management server 909-4 writes an end time“Ed-2” into an end time column of a record having a circuitidentification code “CIC-3” in the CIC management table 926-2B (FIG.159), and forms a release-completion IP packet 938B (FIG. 181, RLCpacket) in order to notify a reception of the release IP packet 937B,thus sending it back to the telephone management server 908-4 (StepB84).

[0665] The telephone management server 908-4, receiving the Step B84,notifies a release instruction to the radio base point 902-3 by way ofthe proxy mobile phone server 908-6 and network node unit 908-1 (StepsB85 to B87). The radio base point 902-3 can also notify a disconnectinstruction to the telephone set 905-6 via the radio communication path917-5 (Step B70, option). The radio base point 902-4 notifies adisconnect instruction to the telephone set 905-8 (Step B79) and arelease report to the telephone management server 909-4 through theproxy mobile phone server (Steps B81 to B83). The telephone set 905-8can send a disconnect-instruction confirmation signal to the radio basepoint 902-4 (Step B80, option).

[0666] <<Communication Record Deletion>>

[0667] After the Step B73, the telephone management server 908-4 sendsthe circuit identification code “CIC-3” written in the release IP packet937B to the table management server 908-3 (Step B96). The tablemanagement server 908-3 deletes a corresponding communication record, inthe present case, the third-lined record “IB1, IB2, EB1, EB2, MK6, MK5,. . . ” of the unit control table 910-3 (FIG. 138) (Step B97).Similarly, the telephone management server 909-4, after the step B76,extracts the “CIC-3” from the received IP packet 937B and sends it tothe table management server 909-3 (Step B98). The table managementserver 909-3 deletes a corresponding communication record, in thepresent case, the fourth-lined record “IB2, IB1, EB2, EB1, MK5, MK6, . .. ” of the unit control table 910-4 (FIG. 139) (Step B99).

[0668] <<Release Report Option and Radio Channel Disconnection>>

[0669] The telephone management server 909-4, receiving a release report(Step B83), is allowed to forward an IP packet confirming the releasereport. The IP packet confirming the release report reaches the radiobase point 902-4 by way of the proxy mobile phone server 909-6 andfurther network node unit 909-1 (Steps B90 a to B90 c). Furthermore, thetelephone management server 909-4 is allowed to forward an IP packetcontaining a radio channel disconnect signal. The IP packet containing aradio channel disconnect signal passes the proxy mobile phone server909-6 and network node unit 909-1, to reach the base point 902-4 (StepsB91 a to B91 c). When the radio base point 902-4 forwards the IC packetcontaining a radio channel disconnection confirmation signal to thenetwork node unit 909-1, the IP packet passes the network node unit909-1 and proxy mobile phone server 909-6 to reach the telephonemanagement server 909-4 (Steps B92 a to B92 c). Note that the steps B90a to B90 c, B91 a to B91 c and B92 a to B92 c are an omittable option.

[0670] Similarly, ending the Step B85, the telephone management server908-4 forwards an IP packet containing a radio channel disconnect signalto the proxy mobile phone server 908-6. The IP packet passes the networknode unit 908-1 to reach the base point 902-3 (Steps B88 a to B88 c).The base point 902-3 notifies the radio channel disconnect signal takenout of the IP packet to the telephone set 905-6 via the radiocommunication path 917-5 (FIG. 108) (Step B88 d). The telephone set905-6 forwards the radio channel disconnection confirmation signal tothe radio base point 902-3 through the radio communication path 917-6(Step B89 a). The radio base point 902-3 causes an IP packet containinga radio channel disconnection confirmation signal to reach the telephonemanagement server 908-4 via the network node unit 908-1 and proxy mobilephone server 908-6 (Steps B89 c to B89 d). Note that the Steps B88 a toB88 d and B89 a to B89 d are an omittable option.

[0671] <<Regulating the Number of Outgoing Calls and Collection of FeeInformation>>

[0672] In a telephone communication of the communication case 2explained above, the procedure similar to a telephone communication inthe communication case 1 makes it possible to regulate the number ofoutgoing or incoming calls, collect information from the CIC managementtable or unit control table and carry out the process for IP-network 900operation or fee charge.

[0673] <<Mobile Phone Number Registration>>

[0674] Explanation is made on a registration method of a mobile phoneand setting of a communication record of a unit control table in thecommunication case 2, with reference to FIGS. 108 and 211.

[0675] The user 990-2 of a mobile phone 905-6 defines an external IPaddress “EB1” and telephone number “TN3” for use by the mobile phone905-6 according to an operation rule of the IP network 900 or byconsultation with the common carrier, and further offers an applicationfor utilizing the mobile phone 991-2, including at least a user name andpayment of communication fee, to a telephone accepter 991-2. Thetelephone accepter 991-2 provides terminal-unit authenticationinformation “PID3” and notifies the user 990-2 of an external IP address“EB81” of a proxy mobile phone server (Step Q1 in FIG. 211).Incidentally, proxy mobile phone servers 906-6,907-6, 908-6 and 909-6have a common value “EB81” as external addresses. Furthermore, secondterminal-unit authentication information “PID-M” can include multicastreception authentication information including multicast serviceidentification symbol and reception permission password thereof andmulticast-authentication-server external address “WA9”.

[0676] Herein, terminal-unit authentication information “PID3” isprovided for a combination of an external IP address “EB1” and atelephone number “TN3”, which is handled as a secret value not to beopened to the third person other than the user 990-2. The user 990-2sets the mobile phone 905-6 with a telephone number “TN3”, external IPaddress “EB1”, terminal-unit authentication information “PID3”, externalIP address “EB81” of the proxy mobile phone server, second terminal-unitauthentication information “PID-M” (option). Then, the accepter 991-2notifies acceptance information to a user service server 992-2 (StepQ2). The user service server 992-2 holds the acceptance information inits database (Step Q3).

[0677] Next, the user service server 992-2 notifies, at least, atelephone number “TN3” and terminal-unit authentication information“PID3” to the telephone management server 909-4 (Step Q4). The userservice server 992-2 is selected with the telephone management server909-4 according to an operation rule of the IP network 900 (e.g.selected with a telephone management server located neargeographically). The telephone management server 909-4 notifies, atleast, a telephone number “TN3” and terminal-unit authenticationinformation “PID3” to the telephone number server 909-5 (Step Q5). Thetelephone number server 909-5 notifies acquisition information to asuperior telephone number server 995 (Step Q6). The telephone numberserver 995 holds therein, at least, a telephone number “TN3” andterminal-unit authentication information “PID3” (Step Q7).

[0678] Furthermore, the multicast reception authentication informationcan be held (option). The user service server 992-2 can request thesuperior telephone number server 995 to rewrite or delete a content ofthe superior telephone number server 995, through the telephonemanagement server 906-4 or directly without through the same.

[0679] <<Variation>>

[0680] The Steps Q5 to Q7 can be changed to the following Step Q5 x.Namely, the telephone management server 909-4 notifies the superiortelephone number server 995 of, at least, a telephone number “TN3” andterminal-unit authentication information “PID3” (Step Q5 x). Thetelephone number server 995 holds therein the received telephone number“TN3” and terminal-unit authentication information “PID3”.

[0681] <<Initial Position Registration of Mobile Phone>>

[0682] Explanation is made on a method that the mobile phone 905-6registers its position to the IP network 900, with reference to FIGS.108 and 211. Explanation is made on a case that the mobile phone 905-6transmits the radio wave information including a position registrationrequest and unexpectedly connected to the radio base point 902-3 throughthe radio communication line 917-5 (FIG. 108).

[0683] The radio base point 902-3 exchanges information with the mobilephone 905-6 to confirm a communicatability (Step Q10). This confirmationprocedure is made with a communication layer 1 or 2 without thenecessity of using a communication layer 3. Confirming acommunicatability, the mobile phone 905-6 transmits positionregistration request information (Step Q11 in FIG. 211). The positionregistration request information includes a telephone number “TN3” usedby the mobile phone 905-6, terminal authentication information “PID3”,an external IP address “EB1”, and an external IP address “EB81” of aproxy mobile phone server. Incidentally, it is possible as a variationto generate a cipher text C3 with “PID3” as an encryption key and atelephone number “TN3” as a plaintext, in place of the terminal-unitauthentication information “PID3” to use a known authenticationtechnique using an external IP address “EB”, a telephone number “TN3”and a cipher text C3. With this, the terminal-unit authenticationinformation “PID3” in secret will not be transmitted over a radiocommunication line.

[0684] The radio base point 902-3 forms an external packet 997-1 (FIG.212) containing a telephone number “TN3” included in the receptioninformation, external IP address “EB1” and terminal-unit authenticationinformation “PID3” or cipher text C3, and sends it toward the proxymobile phone server 908-6. Herein, the external packet 997-1 has asource external IP address “EB1” and a destination external IP address“EB81”. When the external packet 997-1 reaches the network node unit908-1 (Step Q1), used is a fourth-lined record “IB1, IW81, K-zero, EB81,M-zero, M-one, . . . ” of a capsule control table 910-3 (FIG. 138), toform an internal packet 997-2 (FIG. 213). The internal packet 997-2 issent to the proxy mobile phone server 908-6 (Step Q13). Herein, “IW81”is an internal IP address of the proxy mobile phone server 908-6 while“M-one” is an address mask having its every value of “1”. The proxymobile phone server 908-6 receives an internal packet 997-2, and furtherforms an internal packet containing an internal IP address “IB1”contained in a header section of the internal packet 997-2 to send it tothe telephone number server 908-5 (Step Q14). The telephone numberserver 908-5 holds, in a data storage form of a domain-name server, atelephone number “TN3”, external IP address “EB1”, internal IP address“IB1”, terminal-unit authentication information “PID3” or cipher text“C3”, from the received internal packet (Step Q15). Next, the acquiredtelephone number “TN3”, terminal-unit authentication information “PID3”and identification symbol of the telephone number server 908-5 isnotified to the superior telephone number server 995 (Step Q16). Thetelephone number server 995 examines, by comparison, as to whether thetelephone number “TN3” and terminal authentication information “PID3”held in the step Q7 of telephone number registration agrees with thetelephone number “TN3” and terminal-unit authentication information“PID3” acquired in the step Q16, to determine whether a terminal-unitauthentication result is acceptable or unacceptable. Incidentally, in acase that a cipher text C3 is sent in place of the terminal-unitauthentication information “PID3”, used is a known communicationopposite-side authentication technique that a cipher text C3 isgenerated with “PID3” as an encrypt key and telephone number “TN3” as aplaintext, to examine whether the received cipher text C3 agrees withthe generated cipher text C3 so that determination is made as acceptablewhere there is agreement.

[0685] The superior telephone number server 995 reports the telephonenumber server 908-5 of the terminal-unit authentication result (StepQ20). The telephone number server 908-5, when the terminal-unitauthentication result is unacceptable, discards the telephone number“TN3” and terminal-unit authentication information “PID3” held in thestep Q15 (Step Q21). The telephone number server 908-5 reports theterminal-unit authentication result to the mobile phone 905-6 through aproxy mobile phone server 908-6, network node unit 908-1 and radio basepoint 902-3 (Steps Q22 to Q25).

[0686] <<Mobile Phone Position Change>>

[0687] Explanation is made on a case that a mobile phone 905-6 in astate completed an initial-position registration of the mobile-phone ischanged in the position to be connected to the radio base point 902-3via the radio communication line 917-5 to transmit the radio waveinformation including a position change request so that connection isunexpectedly done to the radio base point 902-4 via the radiocommunication line 917-7 (FIG. 108). In order to simplify explanation,explanation is made on a case that the mobile phone 905-6 is changed toa mobile phone 905-6 x (FIG. 108).

[0688] The radio base point 902-4 exchanges information with the mobilephone 905-6 x, to confirm a communicatability (Step Q10 x in FIG. 214).The mobile phone 905-6 x transmits position registration requestinformation (Step Q11 x). The position registration request informationincludes a telephone number “TN3” to be used by the mobile phone 905-6x, terminal-unit authentication information “PID3”, an external IPaddress “EB1” mentioned before, and an external IP address “EB81” of theproxy mobile phone server. The radio base point 902-4 forms an externalpacket similar to an external packet 997-1 (FIG. 212) containing atelephone number “TN3” included in reception information, external IPaddress “EB1” and terminal-unit authentication information “PID3”, andsends it toward the proxy mobile phone server 909-6. Herein, theexternal packet has a source external IP address “EB1” and a destinationexternal IP address “EB81”. When the external packet reaches the networknode unit 909-1 (Step Q12 x), used is a fifth-lined record “IB2, IW84,K-zero, WA8, M-zero, M-one, . . . ” to form an internal packet similarto the internal packet 997-2 (FIG. 213). The internal packet is sent tothe proxy mobile phone server 909-6 (Step Q13 x). The proxy mobile phoneserver 909-6 receives the internal packet, and further forms a newinternal packet containing an internal IP address “IB2” included in aheader section of the internal packet, sending it to the telephonenumber server 909-5 (Step Q14 x). The telephone number server 909-5holds therein, from the received internal packet, a telephone number“TN3”, external IP address “EB1”, internal IP address “IB2” andterminal-unit authentication information “PID3” according to a datastorage form of a domain name server (Step Q15 x), and notifies thesuperior telephone number server 995 of the acquired telephone number“TN3” together with an identification symbol of the telephone numberserver 909-5 (Step Q16 x).

[0689] The telephone number server 995 examines by comparison whetherthere is agreement between the telephone number “TN3” and terminal-unitauthentication information “PID3” held in the Step Q7 (FIG. 211) oftelephone number registration and the telephone number “TN3” andterminal-unit authentication information “PID3” acquired in the Step Q16x, thereby determining whether a terminal authentication result isacceptable or unacceptable. When unacceptable, the superior telephonenumber server 995 notifies the telephone number server 909-5 thatterminal authentication is unacceptable (Step Q17 x). The telephonenumber server 909-5 discards the telephone number “TN3” andterminal-unit authentication information “PID3” held in the step Q15 x(Step Q18 x) thus suspending the subsequent process.

[0690] When the terminal-unit authentication result is acceptable, thesuperior telephone number server 995 notifies the telephone numberserver 908-5 of a position change request to the terminal unit 905-6 xand IP address “IP909-5” of the telephone number server 909-5 (Step Q19x). The telephone number server 908-5 stores all the pieces ofinformation concerning the mobile phone 905-6 held in the Step Q15 (FIG.211) in an IP packet formed with a destination IP address “IP909-5”, andsends it to the telephone number server 909-5 (Step Q20 x).Incidentally, the telephone number server 908-5 discards the informationalready transmitted. The telephone number server 909-5 can hold theinformation concerning the mobile phone 905-6 acquired in both procedureof Steps Q20 x and Q15 x. However, a position of the mobile phone isgiven as 905-6 x. The telephone number server 909-5 reports theterminal-unit authentication result to the mobile phone 905-6 x by wayof the proxy mobile phone server 909-6, network node unit 909-1 andradio base point 902-4 (Steps Q22 x to Q25 x).

[0691] <<Variation of Collective Management by Superior Telephone NumberServer>>

[0692] Explanation is made on a method that the superior telephonenumber server 995 manages the information concerned with mobile-phonenumber, IP address and the like and the telephone number servers 906-5to 909-5 serve for only the fixed telephone sets, wherein the telephonenumber servers 906-5 to 909-5 are not involved in the registration andposition change procedures for the mobile phones.

[0693]FIG. 215 shows another method for carrying out a mobilephone-registration procedure. The difference from FIG. 211 is in aprocedure that the process by the telephone number servers 908-5 and909-5 shown in FIG. 211 is relocated to a superior telephone numberserver 995. Accordingly, FIG. 215 does not include the telephone numberservers 908-5 and 909-5. At first, the Steps U1 to U4 are carried out,wherein the Steps Q1, Q2, Q3, Q4 in FIG. 211 are replaced with the StepsU1, U2, U3, U4 in FIG. 215. Then, the telephone management server 909-4makes notification directly to the superior telephone number server 995(Step U5). The telephone number server 995 holds related information(Step U7). Furthermore, the Steps U10 to U13 are carried out, whereinthe Steps Q10, Q11, Q12, Q13 in FIG. 211 are replaced with the Steps U1,U2, U3, U4 in FIG. 215. Then, the proxy mobile phone server 908-6 makesnotification directly to the superior telephone number server 995 (StepU14). The telephone number server 995 carries out a terminal-unitauthentication procedure and the like (Step U15) and notifies the proxymobile phone server 908-6 of a process result (Step U20). Next, theSteps U23 to U25 are carried out, wherein the Steps Q23, Q24, Q25 inFIG. 211 are replaced with the Steps U23, U24, U25 in FIG. 215.

[0694]FIG. 216 shows another method for carrying out a mobile-phoneregistration procedure. The difference from FIG. 214 lies in that theprocedure by the telephone number servers 908-5 and 909-5 shown in FIG.214 is relocated to a superior telephone number server 995. At first, aprocedure is carried out wherein the Steps Q10 x, Q11 x, Q12 x, Q13 x inFIG. 214 are replaced with the Steps U10 x, U11 x, U12 x, U13 x in FIG.216. Then, the proxy mobile phone server 909-6 makes notificationdirectly to the superior telephone number server 995 (Step U14 x). Theproxy mobile phone server 909-6 holds related information (Step U21 x)and notifies a process result to the proxy mobile phone sever 909-6(Step U22 x). Next, a procedure is carried out, wherein the Steps Q23 x,Q24 x, Q25 x in FIG. 214 are replaced with the Steps U23 x, U24 x, U25 xin FIG. 216.

[0695] In the communication case 2, the proxy telephone server 908-2 cantake the place of the proxy mobile phone server 908-6 by means that theserver 908-2 includes the function of the proxy mobile phone server908-6, and the server 908-6 can be deleted.

[0696] <<Communication Case 3: Communication between Mobile Phone andFixed Telephone Set>>

[0697]FIG. 182 is a diagram explaining a telephone communication of froma mobile phone 905-6 to a fixed telephone set 905-4. The telephone set905-6 has a telephone number “TN3” and t he telephone set 905-4 has atelephone number “TN2”. In the present communication case 3, the callingmobile phone 905-6 side, i.e. a calling UNI interface (communicationprocedure between the radio base point 902-3 and the telephonemanagement server 908-4) agrees with the calling UNI, interface(communication procedure between the radio base point 902-3 and thetelephone management server 908-4) explained using FIGS. 143 and 144.Also, in the present case, the called fixed telephone set 905-4 side,i.e. a called UNI interface (communication procedure between thetelephone management server 909-4 and the media router 903-4) agreeswith the called UNI interface (communication procedure between thetelephone management server 909-4 and the media router 903-4) explainedusing FIG. 109. Naturally, the communication procedure between thetelephone management server 908-4 and the telephone management server909-4 (NNI interface) is standardized within the IP network 900.

[0698] <<Connection Phase>>

[0699] When the telephone set 905-6 forwards a call connect request, aradio channel connect request signal is conveyed to the radio base point902-3 (Step B01). The radio base point 902-3 sends back a call connectrequest acceptance (Step B02). Next, the telephone set 905-6 forwards acall set request to the radio base point 902-3 (Step B03). When theradio base point forwards a call set request, the call set request issent to the telephone management server 908-4 by way of the network nodeunit 908-1 and proxy mobile phone server 908-6 (Steps B04 to B06). Thetelephone management server 908-4 makes an inquiry to the telephonenumber server 908-5, thereby obtaining an answer (Steps B07, B08).

[0700] Next, the telephone management server 908-4 forwards a call setacceptance and authentication request to notify it to the telephone set905-6 by way of the proxy mobile phone server 908-6, network node unit908-1 and radio base point 902-3 (Steps B09 to B12). The telephone set905-6 sends an authentication answer representative of a terminal-unitcorrectness in a reverse direction to the above (Steps B13 to B16). Thetelephone management server 908-4 forwards an IP packet containing aterminal-unit authentication properness/improperness in a reversedirection to the above (Steps B17 to B20). Next, the telephonemanagement server 908-4 forms an IAM packet for a call set request andsends it to the telephone management server 909-4 (Step A 21). The NNIinterface is standardized within the IP network 900. The calling UNI isthe same as the calling UNI in the communication case 2, while thecalled UNI is the same as the called UNI in the communication case 1.Accordingly, from now on, the implementation of the communicationprocedure shown in FIG. 182 provides an explanation that a telephonecommunication is enabled from the fixed telephone set 905-1 to themobile phone 905-8.

[0701] <<Communication Case 4: Communication Between Fixed Telephone Setand Mobile Phone>>

[0702]FIG. 183 is a diagram explaining a telephone communication of fromthe fixed telephone set 905-1 to the mobile phone 905-8. The telephoneset 905-1 has a telephone number “TN1” and the telephone set 905-8 has atelephone number “TN4”. In the present communication case 4, the callingfixed telephone set 905-1 side, i.e. a calling UNI interface(communication procedure between the media router 903-1 and thetelephone management server 906-4) agrees with the calling UNI interface(communication procedure between the media router 903-1 and thetelephone management server 906-4) explained using FIG. 109. Also, inthe present case, the called mobile phone 905-8 side, i.e. a called UNIinterface (communication procedure between the telephone managementserver 909-4 and the radio base point 902-4) agrees with the called UNIinterface (communication procedure between the telephone managementserver 909-4 and the radio base point 902-4) explained using FIGS. 142and 143. The communication procedure (NNI interface) of between thetelephone management server 906-4 and the telephone management server909-4 is standardized within the IP network 900.

[0703] With the above configuration, when the telephone set 905-6 sendsa call connect request (Step A01), the media router 903-1 sends back acall connect request acceptance (Step A02) and the media router 903-1sends a call set request (Step A04). The call set request reaches thetelephone management server 906-4 (Steps A04 to A06). The telephonemanagement server 906-4 makes an inquiry to the telephone number server906-8, thereby obtaining an answer (Steps A07, A08). Next, the telephonemanagement server 906-4 sends an IP packet (IAM packet) for a call setrequest to the telephone management server 909-4 (Step A21). The IAMpacket has a content of a call notification reaching the telephone set905-8 by way of a proxy mobile phone server 909-6, network node unit909-1 and radio base point 902-4 (Steps B21 to B25). The NNI isstandardized within the IP network 900. The calling UNI is the same asthe calling UNI in the communication case 1, while the called UNI is thesame as the called UNI in the communication case 2. Accordingly, fromnow on, the implementation of the communication procedure shown in FIG.183 provides an explanation that a telephone communication is enabledfrom the fixed telephone set 905-1 to the mobile phone 905-8.

[0704] <<Variation in Communication Cases 1 to 4>>

[0705] The UNI forms of the media router and radio base point can bemanaged by the respective media router and radio base point, to make anotification to the telephone management server. For example, in atelephone communication of from the fixed telephone set 905-1 to thefixed telephone set 905-4 in the communication case 1, the media router903-1 stores a UNI form of media router 903-1 in an IP packet 920 (FIG.110) to notify it to the telephone management server 906-4 (Steps A04 toA06). In a telephone communication of from the mobile phone 905-6 to themobile phone 905-8 in the communication case 2 (FIG. 143), the radiobase point 902-3 stores a UNI form of radio base point 902-3 in an IPpacket 920B (FIG. 145) to notify it to the telephone management server908-4 (Steps B04 to B06). Similarly, the radio base point 902-4 stores aUNI form of radio base point 902-4 in an IP packet to forward it to thenetwork node unit 909-1 (Steps B27 b or B31).

[0706] It is allowed that telephone number servers can be divided intotwo groups, i.e., the group for fixed telephone communications, and thegroup for mobile telephone communications, and the communicationsbetween telephone (mobile) servers can be limited within each group.

[0707] <<Radio Base Point>>

[0708] In this embodiment, the media router or fixed telephone set holdsan IP address and the radio base point or mobile phone holds an IPaddress, which is explained in the below. In FIG. 184, numeral 950-1 isan IP communication network, numeral 950-2 is a network node unit,numeral 951-1 is a radio base point, numeral 951-2 is an IPcommunication line interface section, numeral 951-3 is a radio interfacesection, numeral 952-1 is an analog mobile phone, numeral 952-2 is adigital mobile phone, numerals 952-3 to 953-4 are IP mobile phones, andnumerals 953-1 to 953-4 are radio communication paths.

[0709] An IP packet, containing a telephone line connection controlmessage and digital voice, is communicated over the IP communicationline 950-3 at between the radio base point 951-1 and the network nodeunit 950-2. The IP communication line interface section 951-2 holds aplurality of IP addresses, to manage IP addresses and port numbers bythe use of a channel-IP address correspondence table 959 (FIG. 185). Thecontrol signal or voice signal 958-1 (FIG. 186) forwarded from theanalog mobile phone 952-1 reaches a voice transmitting/receiving section954-1, radio transmitting/receiving section 955-1, radio communicationpath 953-1, radio transmitting/receiving section 956-1 and radiointerface section 951-3 to restore a control or voice signal. Thisreaches the IP communication line interface section 951-2 where thecontrol or voice signal is digitalized and placed onto a payload of anIP packet 957-1. An example using an IP address “EA1” and UDP portnumber 5002 is shown in “. . . , EA1, 5002, CN9531, MID-1000” on a firstline of a radio communication path—IP address correspondence table 959.This shows a radio communication path 953-1 shown at a channel ID“CN9531”. A management ID “MID-1000 is used in billing management of IPaddress utilization. The case with a digital mobile phone 952-2 issimilar to analog mobile phone 952-1. An example using an IP address“EA1” and UDP port number 5004 is shown in “. . . , EA1, 5004, . . . ”on a second line of the radio communication path—IP addresscorrespondence table 959.

[0710] In a case the digital mobile phone 952-3 does not hold an IPaddress, the digital mobile phone 952-3 receives an IP packet 958-3instructing the use of an IP address “EA3” and port number “5012” fromthe IP communication line interface section 951-2 (FIG. 187). Next,sending an IP packet 957-3 (same as 958-4) digitally representing acontrol or voice signal, the IP communication line interface 951-2forwards an IP packet 956-4 onto the IP line 950-3. Next, in a case thedigital mobile phone 952-4 holds an IP address “EA4”, the digital mobilephone 952-4 sends an IP packet 958-5 digitally representing a controlsignal or voice signal. The IP communication line interface 951-2forwards an IP packet 957-4 (same as 958-5) onto the IP line 950-3. Itis important that the IP communication line interface section 951-2manages to lend an IP address “EA3” and port number “5012” to the IPmobile phone 952-3 by a third-lined record “. . . , EA3, 5012, . . . ”of a channel—IP address correspondence table 959, and grasps the IPmobile phone 952-4 holding an IP address “EA4” to set it in an IP packet958-5 by a fourth-lined record”. . . , EA4, . . . ” of the channel—IPaddress correspondence table 959.

[0711] <<Route Telephone Number Server>>

[0712] Explanation is made on another implementing method for acquiringa related IP address or the like from a telephone number in order forapplication where the IP network 900 (FIG. 108) increases in its scale,with reference to FIG. 217.

[0713] Numerals 900-10 to 900-12 are IP networks, numerals 900-13 to900-17 are terminal-unit gateways, numerals 900-18 to 900-21 are relaygateways, numerals 900-23 to 900-27 are media routers, numerals 900-30to 900-32 are radio base points, numerals 900-33 to 900-35 are mobilephones, numerals 900-37 to 900-41 are fixed telephone sets, numerals995-1 to 995-3 are superior telephone number servers, and numeral 995-4is a route telephone number server. The relay gateways are connectedtogether through IP communication lines. The IP networks 900-10 to900-12 are managed individually by a common carrier.

[0714] The terminal-unit gateways 900-13 to 900-17 include respectiveindividual telephone number servers similarly to the terminal-unitgateway 901-1 (FIG. 108). The relay gateways 900-18 to 900-21 aredisclosed as the relay gateways connecting between the IP networks by IPcommunication lines in the prior patent application (FIG. 288 or thelike). Similarly to the superior telephone number server 995 (FIG. 108)carrying out the process of acquiring an IP address from a telephonenumber within the IP network 900, the superior telephone number servers995-1 to 995-3 (FIG. 217) respectively carry out processes concerning anrelated IP address or related information from telephone numbers withinthe IP networks 900-10 to 900-13. The superior telephone number servers995-1 to 995-3 is allowed to communicate, with the route telephonenumber server 995-4, an IP packet containing the information concerningtelephone number and IP address (Steps 995-10 to 995-12 in FIGS. 218 and219). Also, the superior telephone number servers 995-1 and 995-3, afterinquiring the route telephone number server 995-4 of another server's IPaddress and acquiring it, is allowed to use the acquired IP address,transmitting and receiving an IP packet containing the informationconcerning a telephone number or IP address (Step 995-13). The IP packetto be transferred between the IP networks 900-10 to 900-12 passesthrough the relay gateway 900-18 to 900-21.

[0715] The telephone number server in the terminal-unit gateway 900-13presents a telephone number “TN900-35” to the superior telephone numberserver 995-1 in order to acquire an IP address or related informationfrom the telephone number “TN900-35” of the mobile phone 900-35. Thesuperior telephone number server 995-1 presents the telephone number“TN900-35” to the route telephone number server 995-4. The routetelephone number server 995-4 presents the telephone number “TN900-35”to the superior telephone number server 995-3. Thereupon, the superiortelephone number server 995-3 sends back an IP address or relatedinformation concerning the telephone number “TN900-35”. The IP packetcontaining the IP address or related information concerning thetelephone number “TN900-35” flows in a reverse direction to the above,to pass the route telephone number server 995-4 and superior telephonenumber server 995-1, being delivered to a telephone number server in theinquiry-source terminal-unit gateway 900-13. The procedure for acquiringa related IP address between a plurality of telephone number servers canadopt a known art as a domain name server.

[0716] Meanwhile, the telephone number server within the terminal-unitgateway 900-13 inquires the superior telephone number server 995-1 of atelephone number “TN900-40” of the fixed telephone set 900-40 to acquirean IP address and related information, which can be carried outsimilarly to the foregoing series of procedures. In brief, in a caseconnected with a plurality of IP networks, the telephone number serverin the IP network 1 can inquire and acquire an IP address and relatedinformation concerning a telephone number “TEL2” managed by the superiortelephone number server 2, through the superior telephone number server1, the route telephone number server and the superior telephone numberserver 2 in the IP network 2.

[0717] <<Variation for Invoking Superior Telephone Number Server>>

[0718] In the telephone communication procedure of from the fixedtelephone set 905-1 to the fixed telephone set 905-4 shown in FIG. 109,the procedure (Steps A07, A08) related by the telephone managementserver 906-4 and telephone number server 906-5 can be changed to anotherprocedure for invoking the superior telephone number server 995, whichis explained with reference to FIG. 220. In FIG. 220, the telephonecommunication procedure steps excluding the Steps A07 x, A07 y, A08 xand A08 y are all the same as the Steps shown in FIG. 109. Explanationis made on the different Steps A07 x, A07 y, A08 x and A08 y.

[0719] In the Step A07 of FIG. 220 (same as the Step A07 of FIG. 109),the telephone number server 906-5 receives an IP packet containing aninquiry on a destination telephone number “TN2” and source telephonenumber “TN1”. The telephone number server 906-5 holds theaddress-related information about the telephone number “TN1” (variousaddresses and UNI kind). However, in a case without having the addressinformation concerning the telephone number “TN2”, the telephone numberserver 906-5 sends and inquires the information concerning the telephonenumber “TN2” to the superior telephone number server 995 (Step A07 x).The superior telephone number server 995 sends a telephone number “TN2”to the telephone number server 909-5 holding the address-relatedinformation about the telephone number “TN2”, to inquire of addressrelated information (Step A07 y). The telephone number server 909-5answers the address-related information concerning the telephone number“TN2”. Namely, answered are a media router address “EA2” and internal IPaddress “IA2” at an end of the communication line, an external IPaddress “EA82” and internal IP address “IA82” of the proxy telephoneserver, an IP address “IA92” of the telephone management server and amedia-router UNI kind. The answered address-related information passesthe superior telephone number server 995 (Step A08 x) and further thetelephone number server 906-5 (Step A08 y) to reach the telephonemanagement server 906-4 (Step A08). Note that answer is provided fromthe telephone number server 909-5 directly to the telephone numberserver 906-5 without passing the superior telephone number server 995.The series of Steps A07 x, A07 y, A08 x and A08 y can be carried out dueto the recursive call function of a known domain name server.

[0720] Furthermore, in a procedure of the telephone communication fromthe mobile phone 905-6 to the mobile phone 905-8 shown in FIG. 143, aprocedure is possible to invoke the superior telephone number server995, which is explained with reference to FIG. 221. In FIG. 221, thetelephone communication procedure steps excluding the Steps B07 x, B07y, B08 x and B08 y are all the same as the Steps shown in FIG. 143.Explanation is made on the different Steps B07 x, B07 y, B08 x and B08y. The telephone management server 908-4, receiving an IP packetcontaining an inquiry concerning a destination telephone number “TN4”and source telephone number “TN3” (Step B06), inquires the superiortelephone number server 995 of the address information or the likeconcerning the telephone number “TN4” (Step B07 x). The superiortelephone number server 995 inquires the telephone number server 909-5of the address information or the like concerning the telephone number“TN4” (Step B07 y). The telephone number server 909-5 responds ananswer, including the address-related information to the question, tothe telephone management server 908-4 (Step B08 y) via the superiortelephone number server 995 (Step B08 x).

[0721] <<Communication Case 5: Multimedia Terminal-to-TerminalCommunication Based on Common Channel Signaling System>>

[0722]FIG. 189 is a diagram explaining multimedia terminal-to-terminalcommunication based on call connection control. In contrast to thecommunication in the communication case l (FIG. 109) carrying out acommunication with call connection control by way of the fixed telephoneset 905-1, the media router 903-1, the network node unit 906-1, theproxy telephone server 906-2, the telephone management server 906-4, thetelephone management server 909-4, the proxy telephone server 909-2, thenetwork node unit 909-1, the media router 903-4 and the fixed telephoneset 905-4, the communication shown in FIG. 189 is a communication usinga multimedia terminal unit 905-10 in place of the fixed telephone set905-1 and a multimedia terminal unit 905-16 in place of the fixedtelephone set 905-4. The multimedia terminal unit 905-10 and 905-16 are,for example, terminal units, desktop data processing units (personalcomputers or the like) or telephone sets having a function to transmitand receive a voice and still image, a portable-type data assistances(PDA), terminal units, telephone sets, cellular phones, TV transceivershaving a function to transmit and receive a voice and still or movingimage or a variety of data, or terminal units integrated with thefunctions of these units and appliances.

[0723] The Steps A01 to A60 for terminal-to-terminal communicationconnection shown in FIG. 109 correspond, one to one, the Steps J01 toJ60 for terminal-to-terminal communication connection shown in FIG. 189.The Steps A70 to A80-1 correspond, one to one, the Steps J70 to J80-1for terminal-to-terminal communication connection shown in FIG. 189. Theterminal-to-terminal communication connecting control method of betweenthe terminal unit 905-1 and the terminal unit 905-4 is the same as theterminal-to-terminal communication connecting control method of betweenthe terminal unit 905-10 and the terminal unit 905-16.

[0724] A step J68 (FIG. 189) shows a range of terminal-to-terminal mediacommunication, a step J69-1 a terminal-to-terminal high-levelcommunication start procedure, a step J-69-2 a terminal-to-terminalmedia communication, and a step J69-3 a terminal-to-terminal high-levelcommunication closing procedure. Steps J69-1 and J69-3 belong to aterminal-to-terminal high-level communication control layer, and a stepJ69-2 belongs to a terminal-to-terminal media communication layer.

[0725] Furthermore, explanation is made on a method that the terminalunits 905-10 and 905-16 carry out terminal-to-terminal communication byusing telephone numbers, with reference to FIGS. 190 and 191. FIG. 190is a diagram of FIG. 108 simplified to explain a communication betweenthe terminal units 905-10 and 905-16. The servers within theterminal-unit control sections 914-1 (FIG. 108) and 914-4 are omittedlydescribed, hence omitting some procedures of within the terminal-unitcontrol section 914-1. FIG. 191 is a simplification of FIG. 173.

[0726] A call connect request is forwarded from the terminal unit 905-10(Step J01). The media router 903-1 sends back a call connect requestacceptance (Step J02). Subsequently, the media router 903-1 sends a callset request, including a telephone number “TN5” of the terminal unit905-10 as an origin and telephone number “TN6” of the terminal unit905-16 as a destination, to the terminal-unit control section 914-1within the terminal-unit gateway 901-1 (Step J04). The terminal-unitcontrol section 914-1 forms an initial address message (IAM packet)containing the telephone numbers “TN5” and “TN6” and forwards it intothe IP network 900 (Step J21). The IAM packet reaches the terminal-unitcontrol section 914-4 via the control communication line 912-1 (FIG.108). The terminal-unit control section 914-4 notifies an incoming-callnotification obtained by receiving the IAM packet to the terminal unit905-16 (Step J25) via the media router 903-4 (Step J24). The mediarouter 903-4 replies (Step J31). Subsequently, the terminal-unit controlsection 914-4 forms an address completion message (ACM packet) notifyinga possibility of reception of a call set request based on the IAMpacket, and sends it back to the terminal-unit control section 914-1(Step J34). The ACM packet reaches the terminal-unit control section914-1 via the control communication line 912-1. Furthermore, it ispossible to send the information representative of a possibility ofreception of within the ACM packet to the media router 903-1 (Step J37,option).

[0727] When the terminal unit 905-16 notifies an in-calling to the mediarouter 903-4 (Step J40), the media router 903-4 notifies an in-callingto the terminal-unit control section 914-4 (Step J41). The terminal-unitcontrol section 914-4, receiving an in-calling, forms and forwards acall message “CPG” (Step J44). The call message “CPG” is transferredwithin the IP network 900, to reach the terminal-unit control section914-1. The terminal-unit control section 914-1 notifies an in-calling tothe terminal unit 905-10 via the media router 903-1 (Steps J47, J48).

[0728] When the terminal unit 905-16 responds, the response passes themedia router 903-4 (Step J50) to reach the terminal-unit control section914-4 (Step J51). The terminal-unit control section 914-4 forms andforwards an answer message (ACM packet) (Step J54). The ACM packet istransferred within the IP network 900 to reach the terminal-unit controlsection 914-1. The terminal-unit control section 914-1 notifies theresponse to the terminal unit 905-10 via the media router 903-1 therebyenabling communication between the terminal units (Steps J57, J58). Notethat the terminal unit 905-10 can forward a confirmation of answer alsoto the media router 903-1, subsequently to the Step J58 (Step J59,option). Meanwhile, the media router 903-4 can forwards a confirmationof answer to the terminal unit, subsequently to the Step J50 (Step J60,option).

[0729] Due to the above procedure, a communication path through the IPnetwork was established by the procedure based on a common channelsignaling system between the terminal units 905-10 and 905-16established. Next, the terminal units 905-10 and 905-16 carry out aterminal-to-terminal high-level communication start procedure (StepJ69-1). The terminal-to-terminal high-level communication startprocedure can perform, for example, opening a voice image communicationlogic channel, communication mode selection, flow control designation,terminal-capability information exchange and so on. Next, a plurality ofIP packets storing voice, images, text data and the like arecommunicated between the terminal unit 905-10 and the terminal unit905-16, thus effecting terminal-to-terminal media communication (StepJ69-2). The IP packet storing voice, images, text data and the like istransferred through the network node unit 906-1 and media-transfercommunication line 913-3. When the terminal-to-terminal mediacommunication ends, the terminal units 905-10 and 905-16 carry out theopened terminal-to-terminal high-level communication closing procedure(Step J69-3).

[0730] Next, when the terminal unit 905-10 issues a release request(Steps J70, J71), a REL packet notifying a release is forwarded from theterminal-unit control section 914-1 (Step J74). The terminal-unitcontrol section 914-4 is sent back with a RLC packet notifying acompletion of release (Step J84). The terminal-unit control section914-4 notifies a release notification to the terminal unit 906-16 (StepsJ78, J79) to receive a confirmation of release (Step J80, J81). Themedia router 903-4 can forward a release report confirmation (StepsJ80-1, option). Also, the terminal-unit control section 914-1 notifiesare lease notification to the media router 903-1 (Step J87). The mediarouter 903-1 can forward a confirmation of release (Step J70-1, option).By the above procedure, released is the communication path having beenset up for terminal-to-terminal communication.

[0731] In FIG. 192, there is a UDP layer in a level above an IPcommunication layer. A line connection control (or signaling connectioncontrol, circuit connection control) layer based on the No. 7 commonchannel signaling system is provided in a level above the UDP layer. Aterminal-to-terminal high-level communication control layer is providedin a level above the line connection control layer. A communicationmedia layer is provided in a level above the terminal-to-terminalhigh-level communication control layer.

[0732] It is possible to place the line connection control layer basedon the common channel signaling system in a level above the IP layer,thereby omitting the UDP layer. Incidentally, the technique of placingthe line connection control layer in a level above the IP layer isdisclosed in the prior patent (FIG. 206 in Embodiment 13, or the like).The line connection control layer placed in the level above the IP layeris defined as a new protocol to provide, in a header beginning of a newprotocol segment of the line connection control layer, a port field (16bits×2, when IPv4) in a form similar to a port field in a header of aUDP or TCP segment. This can overcome the defect that the UDP layer isomitted to disable the use of a port number. The new protocol segment ofthe line connection control layer is in a form similar to the UDP or TCPsegment. There is an expectation on a merit that the IP communicationunit is simplified. The technique, placing the line connection controllayer based on a common channel signaling system in a layer above an IPlayer, is applicable to all of communication cases 1 to 5.

[0733] <<Communication Case 6: Multimedia Terminal-to-TerminalCommunication Set with Communication Records>>

[0734]FIG. 193 is a multimedia terminal-to-terminal communication method(communication record dynamical setting method) not based upon thecommon channel signaling system for setting a communication record.Explanation is made on a method of communication that the IP terminalunit 905-11 and the IP terminal unit 905-14 communicate respectivelythrough telephone management servers 906-4 and 907-4.

[0735] The terminal unit 905-11 has an identification name “TN7” and anIP address “EA7”. The terminal unit 905-14 has an identification name“TN8” and an IP address “EA8”. Meanwhile, the terminal unit 905-11performs transmission by using a port number “7070” while the terminalunit 905-14 performs transmission by using a port number “7080”. The IPterminal units 905-11 and 905-14 are also multimedia terminal units totransmit and receive text data, digitalized voice, still or movingimages by storing them in an IP packet. For example, the identifier“TN7” and “TN8” can be mail address and/or an identification code (URL)of home page provided by WWW server.

[0736] <<Connection Phase>>

[0737] An IP packet 971 (FIG. 195) is forwarded from the IP terminalunit 905-11 (Step K01 in FIG. 193). The IP packet 971 passes the mediarouter 903-1 (Step K04), to pass the network node unit 906-1 where it isencapsulated into an internal IP packet 972 (FIG. 196) to reach theproxy telephone server 906-2 (Step K05) and turn into an IP packet 973(FIG. 197), reaching the telephone management server 906-4 (Step K06).The IP packet 971 includes at least the “TN7”, “TN8” and “7070”Incidentally, the technique that the IP packet forwarded from the IPterminal unit 905-11 passes the media router and reaches the networknode unit without changing the IP address is applied with a known artdescribed in the prior application patent (Japanese Patent ApplicationNo. 078270/2001).

[0738] <<CIC Management Table Preparation>>

[0739] The telephone management server 906-4 defines a CIC number“CIC-8” from a source identification name “TN7” and destinationidentification name “TN8” obtained by reading the IP packet 973 byapplying a rule previously defined in the IP network 900. Furthermore,the telephone management server 906-4 sends to the telephone numberserver 906-5 an IP packet 974 for inquiring various IP addresses relatedto the destination identification names “TN7” and “TN8”, a UNI kind ofthe media router 903-3 the destination IP terminal unit 905-14 is toconnect, and a port number the destination IP terminal 905-14 (FIG. 198)is to use (Step K07), to obtain an IP packet 975 (FIG. 199) containingan answer to the inquiry (Step K08).

[0740] The telephone management server 906-4 furthermore prepares a CICmanagement table 976-1 (FIG. 200) and writes therein a CIC number“CIC-8”, a UNI kind “UNI1” of the media router 903-1, a UNI kind “UNI2”of the media router 903-3, a source identification name “TN7”, adestination identification name “TN8”, an external IP address “EA7” andinternal IP address “IA8”, a procedure partition “IAM”, a write time“St-7” and an elapse time (timer value) to an end “Time7”. The kind ofinformation content to be written in the CIC management table 976-1(FIG. 200) is defined relying upon a UNI kind “UNI1” of the media router903-1.

[0741] <<Regulation in the Number of IP Packets on Each Line>>

[0742] The telephone management server 906-4 takes a source IP address“EA7” out of the CIC management table 976-1 and writes it to atransmission-count management table under control of the telephonemanagement server 906-4. The number of lines in service is increased by“1” and compared with the upper-limit number of lines. Incidentally,where the number of lines in service is greater than the upper-limitnumber of lines, the process is suspended without proceeding to thefollowing connection phase. The transmission-count management table isin the same form as an outgoing-call management table 918 l (FIG. 140).

[0743] <<Notification of Communication Permission>>

[0744] Next, the telephone management server 906-4 forms and forwards aninternal IP packet 978 (FIG. 201) notifying a communicatability betweenthe IP terminal unit 905-11 and the IP terminal unit 905-14 (Step K55).The proxy telephone server 906-2 converts the IP packet 978 into an IPpacket 979 (FIG. 202) and forwards it to the network node unit 906-1(Step K56). An IP packet 980 (FIG. 203) obtained by decapsulation passesthe media router 903-1 (Step K57) to reach the IP terminal unit 905-11(Step K58). The IP packet 980 contains, as a content, an IP address“EA8” and port number “7080” of the destination IP terminal unit 905-14.Incidentally, the telephone management server 906-4, upon forming an IPpacket 978, reads the IP address “EA8” and port number “7080” out of theIP packet 975 (FIG. 199) and writes it to the IP packet 978.

[0745] Next, the telephone management server 906-4 makes reference tothe IP address information of the CIC management table 976-1 and formsan IP packet 977 (FIG. 201) for notifying a preparation of acommunication record required in terminal-to-terminal communication, andsends the IP packet 977 to the telephone management server 907-4 (StepK21). The telephone control server 907-4 receives the IP packet 977, asexplained in the method similarly with other communication cases, andforms the CIC management table 976-2.

[0746] <<Regulation in the Number of Incoming IP Packets on Each Line>>

[0747] The telephone management server 907-4 takes a destination IPaddress “EA8” out of the received IP packet 977 and writes it into anincoming-call-count management table. The number of incoming IP packetson each line is regulated, e.g. the number of lines in service isincreased by “1”.

[0748] <<Communication Record Setting>>

[0749] Following the Step K21, the telephone management server 906-4takes an IP address “EA7, IA7, EA8, IA8” of a first-lined record of theCIC management table 976-1 (FIG. 200) and asks the table managementserver 906-3 (Step K66), so that the table management server 906-3 setsit as a fifth-lined communication record “IA7, IA8, EA7, EA8, MK25,MK26, . . . ” of a unit control table 910-1 (FIG. 136) within thenetwork node unit 906-1 (Step K67). Furthermore, the telephonemanagement server 906-4 sets a time-elapse interrupt timer correspondingto the CIC number “CIC-8” according to a lapse time (timer value)“time7” to an end included in the CIC management table 976-1.

[0750] Similarly, the telephone management server 907-4 takes an IPaddress “EA8, IA7, EA8, IA7” of a first-lined record of the CICmanagement table 976-2 and asks the table management server 907-3 (StepK64), so that the table management server 907-3 sets it as a third-linedrecord “IA8, IA7, EA8, EA7, MK26, MK25, . . . ” of a unit control table910-2 (FIG. 137) within the network node unit 907-1 (Step K65).Furthermore, the telephone management server 907-4 sets a time-elapseinterrupt timer corresponding to the CIC number “CIC-8” according to alapse time “time7” to an end included in the CIC management table 976-2.

[0751] <<Terminal-to-Terminal Communication>>

[0752] The IP terminal unit 905-11, receiving an IP packet 980 (Step K58in FIG. 203), acquires an IP address “EA8” and port number “7080”corresponding to the identification name “TN8” of the IP terminal unit905-14 at the other end of communication. The IP terminal unit 905-11forms an IP packet 981 (FIG. 206) to be sent to the IP terminal unit905-14. The IP packet 981 forwarded from the IP terminal unit 905-11passes the media router 903-1 (Step K68-1) to reach the network nodeunit 906-1 (Step K68-2). This turns into an internal packet 979 by theapplication of the fifth-lined communication record of the unit controltable 910-1 (FIG. 136) having been set in the above. The internal packet982 (FIG. 207) is transferred within the IP network 900 (Step K68-3) toreach the network node unit 907-1 where it is decapsulated to restore anIP packet 981. This is forwarded to pass the media router (Step K684) toreach the terminal unit 905-14 (Step K68-5). The IP packet forwardedfrom the IP terminal unit 905-14 is transferred in a reverse directionover the communication path, thus reaching the IP terminal 905-11 (StepsK69-1 to K69-5). The IP terminals 905-11 and 905-14 properly exchangedata by communicating IP packets.

[0753] <<Communication Record Deletion>>

[0754] When the time-elapse interrupt timer corresponding to the set CICnumber “CIC-8” starts up due to lapse of a predetermined time “time7”,the telephone management server 906-4 instructs the table managementserver 906-3 to delete a relevant communication record in the unitcontrol table 910-1 corresponding the CIC number “CIC-8” (Step K96 inFIG. 193). The table management server 906-3 deletes the communicationrecord (Step K97). Similarly, when the time-elapse interrupt timercorresponding to the set CIC number “CIC-8” starts up due to lapse of apredetermined time “time7”, the telephone management server 907-4instructs the table management server 907-3 to delete a relevantcommunication record in the unit control table 910-2 (Step K98). Thetable management server 907-3 deletes the communication record (StepK99).

[0755] <<Another Delete Method of Communication Record>>

[0756] Explaining with reference to FIG. 194, nearly similar are StepsK01 to K69-5, i.e. steps of from carrying out to a completion ofcommunication exchanging IP packet between the terminal 905-11 and theterminal 905-14 due to issuing an communication request from theterminal unit 905-11. The difference lies in that the telephonemanagement servers 906-4 and 907-4 are both not provided with atime-elapse interrupt timer. When the terminal unit 905-11 forms andforwards an IP packet notifying a communication end (Step K70), the IPpacket reaches the telephone management server 906-4 by way of the mediarouter 903-1, network node unit 906-1 and proxy telephone server 906-2(Steps K71 to K73). The IP packet forwarded from the terminal unit905-11 has a form same as a form of the IP packet to be forwarded in theStep K01, wherein the difference is further inclusion of a notificationof communication end “END”. The IP packet to be forwarded in the StepK72 has a form same as a form of the IP packet 972 (FIG. 196) to beforwarded in the Step K05. Similarly, the IP packet to be forwarded inthe Step K73 has a form same as a form of the IP packet 973 (FIG. 197)to be forwarded in the Step K06. The difference lies in including anotification of communication end “END”.

[0757] Receiving a communication end notification in the Step K73, thetelephone management server 906-4 first uses identification names “TN7”and “TN8” to calculate a CIC number “CIC-8”, and notifies acommunication end of “CIC-8” to the telephone management server 907-4(Step K74). Next, the table management server 906-3 is instructed todelete a relevant communication record in the unit control table 910-1(Step K96 x). The table management server 906-3 deletes the relevantcommunication record (the fifth record) (Step K97 x). Receiving thecommunication end notification of “CIC-8” in the Step K74, the telephonemanagement server 907-4 instructs the table management server 906-3 todelete a relevant communication record (the third record) in the unitcontrol table 910-2 (Step K98 x). The table management server 906-3deletes the relevant communication record (Step K99 x).

[0758] <<Summary of Communication Case 6>>

[0759] The IP network includes the network node unit 1 and the networknode unit 2. The terminal unit 1 forwards to the network node unit 1 anIP packet including an identification name 1 of the terminal unit 1 andidentification name 2 of the terminal unit 2 to request a communication.The internal packet containing the identification name 1 andidentification name 2 reaches the telephone management server 1. Thetelephone management server 1 acquires and sends back an IP address andport number corresponding to the identification name 2 through thetelephone number server. The telephone management server 1 notifies thetelephone management server 2 of a communication request of from theterminal unit 1 to the terminal unit 2. The telephone management server1 asks the table management server 1 to set in the network node unit 1 acommunication record for encapsulating an IP packet to be communicatedbetween the terminal unit 1 and the terminal unit 2. The telephonemanagement server 2 asks the table management server 2 to set in thenetwork node unit 2 another communication record for encapsulating an IPpacket to be communicated between the terminal unit 1 and the terminalunit 2. The terminal unit 1 receives the IP packet containing an IPaddress and port number via the network node unit 1. The terminal unit 1forwards an IP packet having a destination of an IP address and portnumber corresponding to the acquired identification name 2. The IPpacket, in the network node unit 1, is encapsulated into an internalpacket by the use of the above set communication record. The internalpacket is transferred within the communication network to reach thenetwork node unit 2. This, in the network node unit 2, is decapsulatedby the use of the above set communication record, to reach the terminalunit 2. The telephone management server 1 and the telephone managementserver 2, upon elapsing a predetermined time, delete the communicationrecord.

[0760] Incidentally, the identification name 2 corresponds only in an IPaddress but not in a port number. The telephone management server can beprovided not to send back a port number. It is possible, as a variation,for the terminal unit 1 or terminal unit 2 to forward acommunication-end IP packet whereby the telephone management server asksthe table management server 1 to delete a communication record used forthe terminal unit 1 and terminal unit 2.

[0761] <<Another Method for Designating Destination-Terminal PortNumber>>

[0762] The embodiment of communication case 6 showed the example thatthe terminal unit 905-14 used a port number “7080” so that the telephonemanagement server 906-5 gave an answer by storing a port number “7080”in an IP packet 975. Another embodied method is a method that thetelephone management server 906-5 does not answer a port number “7080”.In this case, the IP packet 978 to IP packet 980 do not contain thereina port number “7080”. In this case, a port number “7080” for use by theterminal unit 905-14 is previously notified, e.g. the port number “7080”of the terminal 905-14 is made public by communication carrier thatmanages the IP network 900. The terminal unit 905-11 uses an open portnumber. The CIC management table form and the record having a circuitidentification code “CIC-8” are made common to the communication case 1to the case 5. This can apply a common rule of within the IP network900, e.g. of operation management, fee charge and so on.

[0763] The terminal 905-14, a destination terminal, uses the thirdrecord “IA8, IA7, EA8, EA7, MK26, MK25, . . . ” in the unit controltable 910-2 (see FIG. 137). The port control table (see FIG. 69, etc.)pointed from the record is set to have the port filter 1, whichspecifies both a source port number permitted at sending and adestination port number permitted at receiving. Then, the terminal905-14 only receive the IP packet that destination port number is“7080”, or only sends the IP packet that source port number is “7080”.As the result, the terminal 905-14 does not receive an IP packet whosedestination port number is excluding “7080”, and the terminal 905-11does not receive an IP packet that source port number is excluding“7080”, that enhances communication security.

[0764] <<Secure Socket Communication Between Terminals Using PortFilter>>

[0765] The terminal 2 can perform secure communication by only receivingthe IP packet that includes the port number of the terminal 2, as itsdestination port number, where the terminal 2 makes its identificationname and port number public in advance. Port numbers of the terminal 2can be plural, examples are the port number “25” for e-mail, the portnumber “80” for WWW server. Then, both the e-mail communication andoperation of WWW server can be implemented securely. The IP address ofthe terminal 2 becomes open because of the disclosure of itsidentification name of the terminal 2. By means of limiting the socketnumber of the terminal 905-14 as above, secure socket communication isachieved, where a socket number is a combination of an IP address and aport number.

[0766] Next, a communication between terminal 1 and terminal 2 isdescribed. The terminal 1 shows the identification name of the terminal2 to the telephone number server in the IP network, and obtains the IPaddress of the terminal 2. At this time, the telephone management serverinstructs the table management server to set the port filter 1 (whichspecifies both a destination port number permitted at receiving and asource port number permitted at sending) as pointed from thecommunication record in unit control table in the network node unit 2.Furthermore, the telephone management server instructs the tablemanagement server to set the port filter 2 (which specifies both adestination port number permitted at sending and a source port numberpermitted at receiving).

[0767] Next, the terminal 1 send the external IP packet that destinationIP address is the IP address of the terminal 2, at the network node unit1, the external IP packet is changed to an internal packet, and theinternal IP packet is transported across the IP network, the IP packet,at the network node unit 2, is recovered to the external IP packet, andis sent to the terminal 2, while, the recovered IP packet can berejected if the recovered IP packet does not include the destinationport number which is recorded in the unit control table in the networknode 2. For the inverse transportation of external IP packets, theterminal 2 sends an external IP packet, at the network node 2, theexternal IP packet is changed into an internal IP packet if the externalIP packet includes the source port number which is recorded in thenetwork control table of the network node 2, then the internal IP packettransported across the IP network, and from the internal packet, theexternal IP packet is recovered, and send to the terminal 1.Furthermore, addition to the communication between the terminal 1 andthe terminal 2, at the network node 1, an external IP packet sent fromthe terminal 1 is only changed into an internal IP packet, where theexternal IP packet includes an IP address of the terminal 2, asdestination IP address which is recorded in the network control table ofthe network node 1. Similarly, at the network node 1, an internal IPpacket sent across the IP network is only recovered to an external IPpacket, where the recovered external IP packet includes an IP address ofterminal 2, as source IP address which is recorded in the networkcontrol table of the network node 1.

[0768] In short, a network node unit implements encapsulation (atsending) and decapsulation (at receiving), and the communicationfunction 1 and the communication function 2 using unit control table inthe node, and the network node unit can perform the socket communicationbetween terminals, including more than one of the packet filteringfunction using protocols, priority control or multicast function , wherethe communication function 1 is that inputs an external packet,selecting the external packet and forms into an internal packet,depending the socket number in the external packet, and thecommunication function 2 is that inputs an internal packet and recoversan external packet, selecting the recovered external packet, dependingthe socket number in the recovered external packet.

[0769] Variation is that a network node unit implements the addresstest, and the communication function 1 and the communication function 2using unit control table in the node, and the network node unit canperform the socket communication between terminals, including more thanone of the packet filtering function using protocols, priority controlor multicast function.

[0770] <<Overall Explanation of Communication Cases 1 to 6>>

[0771] <Higher-Level Protocol>

[0772] In the communication cases 1 to 6, the IP packets to becommunicated between the network node unit 906-1, the proxy telephoneserver 906-2 and the telephone management server 906-4 have, in theheader, protocol items that can be properly standardized and used withinthe IP network 900, e.g. can be used as “UDP”. FIG. 192 shows, as aprotocol stack figure, the communication procedures mentioned inCommunication Cases 1 to 4 of this embodiment. There are, from acommunication lower level toward a communication higher level, aphysical layer (first layer), a data link layer (second layer), an IPlayer (third layer), a UDP layer (fourth layer) and a communicationfunction layer showing a line-connection control procedure based on acommon channel signaling system using telephone numbers. In the furtherupper level, there is a high-level communication procedure to be definedby an application. The server-to-server communication within the IPnetwork 900 uses an internal IP packet storing therein a UDP segment.

[0773] The protocol type item, in a header of an IP packet to becommunicated with the telephone management server 906-4, can use furtheras “ICMP”. Otherwise, it is possible to newly define a protocol typeunique to the IP communication network 900 at its inside. The foregoingis true for the protocol type item in a header of an IP packet to becommunicated between the network node unit 909-1, the proxy telephoneserver 909-2 and the telephone management server 909-4.

[0774] This embodiment was an embodiment that the line-connectioncontrol messages (IAM, ACM, CPG, ANM, REL, RLC) are by setting a UDPsegment in a payload of an IP packet (IPv4) defined under RFC791.However, a TCP segment can be provided in place of the UDP segment,which has been explained in the other embodiment. Meanwhile, it ispossible to place a line-connection control layer based on a commonchannel signaling system in a level above the IP layer, forimplementation omitting the UDP layer.

[0775] Telephone number is a telephone number for use on a fixedtelephone set or mobile phone. A telephone number and attendantinformation (IP address, etc.) to a telephone number are to beregistered in the telephone number server via the user service server,telephone management server. Meanwhile, when registering a telephonenumber to be used on a mobile phone to the telephone number server, aterminal-unit authentication procedure is made in order to confirm acorrectness of the telephone number and the attendant information to thetelephone number. The telephone number server holds an external IPaddress of a media router to be connected by a fixed telephone set 1having a telephone number “TN1”, an internal IP address of a logicterminal at an end of a communication line to be connected by the mediarouter, an external IP and internal IP addresses of a proxy telephoneserver, an internal IP address of the telephone management server, and aUNI of the media router. Furthermore, the external IP address of themedia router can be changed to the external IP address of the telephoneset 1, i.e. the telephone number server can hold an external IP addressof the telephone set 1, an internal IP address of the logic terminal, anIP address of the proxy telephone server and telephone managementserver, and a UNI. Namely, the various pieces of information related toa telephone number are held. Furthermore, the telephone number server isallowed to inquire another telephone number server to acquire attendantinformation to the other telephone number “TN2”.

[0776] <Server Integral Mount>

[0777] In carrying out the Communication Cases 1 to 6, the proxytelephone server 906-2, table management server 906-3, telephonemanagement server 906-4 and telephone number server 906-5 of within theterminal-unit gateway 914-1 can be mounted within one computer, to carryout a plurality of servers as application programs of within a computerby providing individual port numbers. Similarly, the servers inplurality within the terminal-unit gateways 914-2 to 914-4 also can becarried out respectively as application programs in plurality within acomputer by providing individual port numbers.

[0778] Also, this is the case that the media router 903-1 or the like isconnected from the terminal-unit control section 914-1 but there is noradio base point. The proxy mobile telephone server 906-6 can beomittedly carried out.

[0779] <Summary 1: Communication with Fixed Telephone Sets and MobilePhones>

[0780] In a terminal-to-terminal communication connection controlprocedure connecting, via a communication line, the terminal unit 1, themedia router 1 or radio base point 1, the telephone management server 1,the telephone management server 2, the media router 2 or radio basepoint 2 and the terminal unit 2, the communication between the terminalunit and the media router or radio base point carries out acommunication procedure on the basis of an individual interface for theterminal unit. The communication procedure of between the media routeror radio base point and the telephone management server is by a UNI forthe media router or radio base point. The communication procedure ofbetween the telephone management server 1 and the telephone managementserver 2 is by an NNI based on the common channel signaling system. Thetelephone management server includes at least a function to carry outthe UNI for the radio base point. The UNI for the media router or radiobase point can be characterized by acquisition through an inquiry fromthe telephone management server to the telephone number server so thatthe telephone management server uses it in communication proceduremanagement. The acquired UNI can be recorded in a CIC management tableof under the management of the telephone management server and used incommunication procedure management. Meanwhile, in a case that thetelephone management server 1 and the telephone management server 2 arein agreement, a method of communication between the telephone sets ispossible. This case is achieved by an implementation omitting theinternal-IP-packet communication between the telephone management server1 and the telephone management server 2. Namely, it is possible to carryout a terminal-to-terminal communication connection control procedureconnecting the terminal unit 1, the media router 1 or radio base point1, the telephone management server, the media router 2 or radio basepoint 2 and the terminal unit, from the communication line. At thistime, omitted is an NNI based on the common channel signaling system atbetween the telephone management server 1 and the telephone managementserver 2.

[0781] The IP network includes two or more network node units. Anexternal packet forwarded from the media router 1 or radio base point 1turns into an internal packet under the control of a unit control tablein a source-sided network node unit. The internal packet is transferredwithin the communication network. The internal packet is restored intoan external packet in a destination-sided network node unit, andforwarded to the media router 2 or radio base point 2. Because of acommunication connecting, from the communication line, the terminal unit1, the media router 1 or radio base point 1, the telephone managementserver 1, the telephone management server 2, the media router 2 or radiobase point 2 and the terminal unit 2, the communication procedure ofbetween the media router or radio base point and the telephonemanagement server is by a UNI for the media router or radio base pointwhile the communication procedure of between the telephone managementserver 1 and the telephone management server 2 is by an NNI based on thecommon channel signaling system, thus carrying out theterminal-to-terminal communication connection control method. Meanwhile,an external packet is inputted at a logic terminal on an externalcommunication line. By defining three sets of the input source-sidedlogic terminal identifying information, a source external IP address inthe external packet and a destination external IP address, defined is adestination incoming-call internal address of an internal packettransfer under the control of a unit control table in the source-sidednetwork node unit. It can be reworded that, under the control of theunit control tables in the source-sided and destination-sided networknode units and control tables in the relay units, an internalcommunication line for internal packet transfer is defined between thesource-sided and destination-sided network node units. The internalpacket is transferred within the communication network and restored toan external packet in the destination-sided network node unit. By usingtwo sets of the input source-sided logic terminal identificationinformation and the destination external IP address in the externalpacket, the source external IP address in the external packet cannot beused.

[0782] By using a communication record ID in the unit control table andspecifying the relevant communication record, it is possible to impose atelephone communication fee for the telephones having at least one beinga mobile phone. In terminal-to-terminal communication, the number ofoutgoing calls can be regulated by the use of an outgoing-callmanagement table. Meanwhile, it can be characterized to regulate thenumber of incoming calls by the use of an incoming-call managementtable. Furthermore, in terminal-to-terminal communication, the operationserver can inquire the telephone management server to acquire theinformation in the CIC control table used in the terminal-to-terminalcommunication thereby imposing a communication fee. The radio base pointincludes an IP communication line interface section, a radio interfacesection and a radio transmitting/receiving section. The radiotransmitting/receiving section can have a telephone communication withany one or more of analog-mobile-phone radio communication path, adigital-mobile-phone radio communication path and an IP-mobile-phoneradio communication path. Also, the IP communication line interfacesection is a radio base point characterized by using a radiocommunication path—IP address correspondence table to manage the IPaddresses to be used by mobile phones. The internal packet can be any ofan IPv4, an Ether frame, an MPLS frame and an HDLC network. Thetechnique explained in the other embodiment can be applied to thepresent embodiment.

[0783] The IP network allows both the communication of between mobilephones of between the mobile phones 1 and the mobile phone 2 and thecommunication between fixed telephone sets of between the fixedtelephone set 1 and the fixed telephone set 2. Furthermore, telephonecommunication is possible between the mobile phone and the fixedtelephone set via the IP network. The user offers an application forregistration of a mobile phone with attaching, at least, a telephonenumber and a mobile-phone address. The accepter notifies the user ofterminal-unit authentication information and a proxy mobile phone serveraddress. The user sets a telephone number, mobile phone address,terminal-unit authentication information and proxy mobile phone serveraddress onto the mobile phone. The superior telephone number serverholds at least a telephone number and terminal authenticationinformation within the telephone number server thereby registering atelephone number of the mobile phone.

[0784] The mobile phone transmits position registration requestinformation. An external packet containing the position registrationrequest information passes the network node unit and turns into aninternal packet to be delivered to a superior telephone number server.The superior telephone number server uses a telephone number andterminal-unit authentication information of the mobile phone included inthe received at least position registration request and a telephonenumber and terminal-unit authentication information held in a telephonenumber registration procedure of a telephone set of an informationmobile phone, to carry out an authentication procedure examining whetherthe mobile phone is a normal telephone set thereby carrying out aninitial position registration of the mobile phone.

[0785] The mobile phone transmits position change request information.An external packet containing the position change request informationpasses the network node unit and turns into an internal packet, thusdelivered to a superior telephone number server. The superior telephonenumber server uses a telephone number and terminal-unit authenticationinformation of the mobile phone included in the received at leastposition registration request and a telephone number and terminal-unitauthentication information held in a telephone number registrationprocedure of a telephone set of an information mobile phone, to carryout an authentication procedure examining whether the mobile phone is anormal telephone set. Next, the information concerning the mobile phoneis sent to the telephone number server or superior telephone numberserver managing a changed position of the mobile phone thereby carryingout a position change procedure of the mobile phone. It is alsopossible, as a variation, for the superior telephone number server tomanage the related information, such as a telephone number and IPaddress of the mobile phone, and for the telephone number server tomanage the related information, such as a telephone number and IPaddress of the fixed telephone set.

[0786] In the network node unit for carrying out communication betweenmobile phones and network node unit for carrying out communicationbetween fixed telephone sets, any is possible of a method for forming aninternal packet from an external IP packet and restoring an externalpacket by the encapsulation and decapsulation function of the networknode unit and a method for making an internal packet by selecting anexternal packet selected by an address inspection using the registrationinformation of within the network node unit explained in the otherembodiment. Also, the network node unit can carry out a packet filterfunction, packet priority control, multicast control and signaturecontrol using a protocol kind and port number. In a case connecting aplurality of IP networks, a telephone number server connected to an IPnetwork 1 can acquire an IP address and related information related to atelephone number “TEL2” managed by a superior telephone number server 2by way of a superior telephone number server 1 connected to the IPnetwork, a route telephone number server, and a superior telephonenumber server 2 connected to an IP network 2.

[0787] <Summary 2: Terminal-to-Terminal Media Communication>

[0788] The terminal unit 1 and the terminal unit 2 uses telephonenumbers establish, via an IP network, a communication path by aline-connection control procedure applying a common channel signalingsystem to the IP network in the IP network, to carry out a terminal-unithigh-level communication start procedure between the two terminal units.Next, terminal-to-terminal media communication is done between theterminals. When the terminal-to-terminal media communication ends, thecommunication path in the IP network is released by a line-connectioncontrol procedure applying a common channel signaling system to the IPnetwork. Thus, a terminal-unit high-level communication closingprocedure can be effected to carry out multimedia communication. Theterminal-to-terminal media communication can communicate an IP packetstoring, for example, voice and images between the terminal unit 1 andthe terminal unit 2, to effect voice image communication. When theterminal-to-terminal media communication ends, the terminal unit 1 andthe terminal unit 2 carry out a terminal-unit high-level communicationclosing procedure for closing the established voice image communicationpath.

[0789] <<Relation to Prior Patent and Prior Patent Application>>

[0790] This embodiment discloses a method for carrying outfixed-telephone and mobile-phone communications on the same IP networkby using a CIC management table including a management function of aterminal-sided UNI and a terminal-to-terminal communication connectioncontrol method having a mobile phone at one end. Disclosed aremultimedia terminal-to-terminal communication to carry outterminal-to-terminal communication connection control based on a commonchannel signaling system and a method for communication by dynamicallysetting a communication record used in IP encapsulation or the like. Theprior patent (Japanese Patent No. 3084681) discloses an IP network basedon an IP encapsulation technique, i.e. IP network that an externalpacket forwarded from a terminal unit turns into an internal packetunder the control of a unit control table of a source-sided network nodeunit, the internal packet being transferred within the communicationnetwork, the internal packet being restored into an external packet in adestination-sided network node unit to be allowed to reach anotherterminal unit. Meanwhile, the prior patent application (2001-78270), inits Embodiment 10 (FIGS. 135 to 160), discloses terminal-to-terminalcommunication connection control, not including a UNI managementfunction, of between a fixed telephone set and a fixed telephone set.

[0791] 9. Embodiment 9 for Carrying out Security ASP

[0792] Explanation is made on a method for implementing ASP service withsecurity by the use of a first function (encapsulation and decapsulationfunction) and second function (protocol filter and port filter) of thenetwork node unit to select an IP packet for communication between anASP server and a user program thereby excluding unspecified IP packets.

[0793] In FIG. 224, numeral 1000 is an IP network, numeral 1001 is anASP site, numerals 1003 and 1004 are terminal units having an IP-packettransmission/reception function, numerals 1005 to 1007 are network nodeunits, and numerals 1011 to 1014 are user programs. The ASP site 1001includes an ASP server 1008, a program 1009 within the ASP site, a WWWprogram 1010, and a database 1026. The network node units 1005 to 1007respectively include unit control tables 1015 to 1017. The unit controltable 1015 includes communication records 1018 and 1019 and filtercontrol records 1022 and 1023. The unit control table 1016 includes acommunication record 1020 and a filter control record 1024. The unitcontrol table 1017 includes a communication record 1021 and a filtercontrol record 1025. The network node units 1005 to 1007 are connectedvia communication lines and routers so that they can mutually send andreceive IP packets.

[0794] The communication records 1018 to 1020 have, in the control itemCTL, a bit position “01” (protocol filter 1, transmission permission)and bit position “02” (protocol filter 2, arrival permission) bothrendered “1”. Furthermore, the communication records 1018 to 1020 have,in the control item CTL, a bit position “05” (port filter 1) rendered“1”. The communication record 1019 has, in the control item CTL, a bitposition “05” (port filter 1) and bit position “06” (port filter 2)rendered “1”. The communication record 1020 has, in the control itemCTL, a bit position “06” (port filter 2) rendered “1”, and thecommunication record 1021 has, in the control item CTL, a bit position“05” (port filter 1) and bit position “06” (port filter 2) rendered “1”.In FIGS. 225 to 227, numerals 1024-1, 1022-1, 1023-1 are protocolcontrol records to be applied to the protocol filter 1, numerals 1024-2,1022-2, 1023-2 are protocol control records to be applied to theprotocol filter 2, while numerals 1024-3, 1022-3, 1023-3 to 1023-5,1025-1 to 1025-3 are port control records. Incidentally, the filtercontrol record 1025 includes port control records 1025-1 to 1025-3 butdoes not include protocol control records.

[0795] <<Transmission from Terminal Unit 1003 to ASP Site 1001>>

[0796] Numeral 1001-1 (in FIG. 228) shows a range of communicationprocedure within the IP network 1000. Although the port number “5000” ofthe ASP server 1008 is previously defined according to a client servermodel, the source port, number “8200” in an external packet 1031 (FIG.229) to be sent by a user program 1011 as a client is defined at a startof communication. The external packet 1031 forwarded from the userprogram 1011 is inputted to the network node unit 1006 (Step R1 in FIG.228) via a communication line and converted into an internal packet bythe use of the communication record 1020 and filter control record 1024.The internal packet passes an internal communication line and router toreach the network node unit 1005 (Step R2). In the network node unit1005, the communication record 1018 and filter control record 1022 areused to restore an external packet. The restored external packet passesa communication line to reach the ASP server 1008 (Step R3).

[0797] When forming an internal packet, the communication record 1020 inthe source-sided network node unit 1006 has, in the control item CTL, aprotocol filter 1 (bit position “01”) of “1”. Accordingly, inspection ismade whether the protocol item value “6” (TCP) in a header 1031-1 of theexternal packet 1031 is included within the protocol control record1024-1 (FIG. 225) or not. In the present case, because the protocolcontrol record 1024-1 includes “6” therein, the protocol filter 1 passesthe examination (transmission permission). Because the port filter 2(bit position “06”) in the control item CTL of the communication record1020 is “1”, inspection is made whether the destination port number“5000” in a payload 1031-2 of the external packet 1031 is includedwithin the port control record 1024-3 (FIG. 225) or not. In the presentcase, because the port number “5000” is included, the port filter 2passes the examination (destination port number at transmission).Incidentally, when the other communication records are also unacceptablein the protocol filter or port filter examination, an internal packet isnot formed.

[0798] Next, when an external packet is restored from the internalpacket, the communication record 1018 in the destination-sided networknode unit 1005 has, in the control item CTL, a protocol filter 2 (bitposition “02”) of “1”. Accordingly, inspection is made whether theprotocol item value “6” (TCP) in a header 1031-1 of an external packet1031 to be obtained by restoration is included within the protocolcontrol record 1022-2 (FIG. 226) or not. In the present case, because“6” is included in the protocol control record 1022-2, the protocolfilter 2 examination (arrival permission) is passed. Furthermore, theport filter l (bit position “05”) in the control item CTL of thecommunication record 1018 is “1”, inspection is made whether thedestination port number “5000” in a payload 1031-2 of an external packet1031 to be restored and obtained is included within the port controlrecord 1022-3 (FIG. 226) or not. In the present case, because the portnumber “5000” is included, the port filter 1 examination (destinationport number at arrival) is passed. Incidentally, when not passedincluding the other communication records in the protocol filter or portfilter examination, an external packet is not formed from the internalpacket.

[0799] <<Sending Back from ASP Site 1001 to Terminal Unit 1003>>

[0800] An external packet 1032 (in FIG. 229) forwarded from the ASP site1001 is inputted to the network node unit 1005 (Step R4) via acommunication line and converted into an internal packet by the use of acommunication record 1018 and filter control record 1022. The internalpacket passes a communication line and router to reach the network nodeunit 1006 (Step R5). In the network node unit 1006, a communicationrecord 1020 and filter control record 1024 are used to restore anexternal packet. The restored external packet passes a communicationline to reach the terminal unit 1003 (Step R6).

[0801] When the internal packet is formed, the communication record 1018within the source-sided network node unit 1005 has, in the control itemCTL, a protocol filter 1 (bit position “01”) of “1”. Accordingly,inspection is made whether the protocol item value “6” in a header1032-1 of the external packet 1032 is included in a protocol controlrecord 1022-1 (FIG. 226) or not. In the present case, because “6” isincluded in the protocol control record 1022-1, the protocol filter 1examination (transmission permission) is passed. Because the bitposition “05” (port filter 1) in the control item CTL of thecommunication record 1018 is “1”, inspection is made whether the sourceport number “5000” in a payload 1032-2 of the external packet 1032 isincluded in a port control record 1022-3 (FIG. 226) or not. In thepresent case, because the port number “5000” is included, the portfilter 1 examination (source port number at transmission) is passed.

[0802] When an external packet is restored, the communication record1020 in the destination-sided network node unit 1006 has, in the controlitem CTL, a protocol filter 2 (bit position “02”) of “1”. Consequently,inspection is made whether the protocol item value “6” in a header1032-1 of an external packet to be restored is included in a protocolcontrol record 1024-2 (FIG. 225) or not. In the present case, because“6” is included in the protocol control record 1024-2, the protocolfilter 2 examination (transmission permission) is passed. Next, thecommunication record 1020 has, in the control item CTL, a bit position“06” (port filter 2) of “1”. Consequently, inspection is made whetherthe source port number “5000” in a payload 1032-2 of an external packet1032 to be restored is included within a port control record 1024-3 ornot. In the present case, because the port number “5000” is included,the port filter 2 examination (source port number at arrival) is passed.

[0803] <<Communication between Terminal Unit 1003 and ASP Site 1001 ofAnother Program>>

[0804] By the client-server communication technique explained in theabove, the program 1012 within the terminal unit 1003 is allowed forcommunication by using, as a server, a WWW program 1010 having a portnumber “80” in the ASP site 1001. Namely, an external packet 1033 issent from the program 1012 to the WWW program 1010. An external packet1034 is sent from the WWW program 1010 to the program 1012. At thistime, the protocol control record uses 1024-1, 1024-2, 1022-1 and 1022-2while the port control record uses 1024-3 and 1022-3.

[0805] <<Communication between Terminal Unit 1004 and ASP Site 1001>>

[0806] By the technique similar to the client-server communicationbetween the user program 1011 and the ASP server 1008 explained in theforegoing, the program 1013 within the terminal unit 1004 is allowed, asa client, for communication with the ASP server 1008 by way of thenetwork node unit 1007, interior of IP network 900 inside and networknode unit 1005. The protocol control record 1023-1 within the networknode unit 1005 uses 1023-1 and 1023-2. The port control record uses1023-3 and 1025-1.

[0807] Incidentally, in the foregoing embodiment, the filter controlrecord 1025 within the network node unit 1007 is in a case not includinga protocol control record. In a process using the port control records1025-1 to 1025-3, when detecting an external or internal packet having aprotocol not including a port number, the external or internal packet isdiscarded. The program 1014 within the terminal unit 1004 is allowed, asa client, for communication with the program 1009 in the ASP site 1001as a server by way of the network node unit 1007, IP network 900 andnetwork node unit 1005, on the principle similar to the foregoing.Furthermore, communication is possible in a reverse relationship of theclient and the server, i.e. the program 1014 is as a server having aport number “25” while the program 1009 is as a client, via the IPnetwork on the principle similar to the foregoing. The program 109 sendsan IP packet 1035 (in FIG. 229) having a destination port number “25”toward the program 1014 while the program 1014 sends an IP packet 1036(in FIG. 229) having a source port number “25” back toward the program1009.

[0808] <<Method of Communication with ASP Site, With Utilizer'sTerminal-Unit Program as Server>>

[0809] In FIG. 230, numeral 1040 is an IP network, numeral 1045 is anASP site, numerals 1046 to 1048 are terminal units having an IP-packettransmission/reception function. The ASP site 1045 includes an ASP siteprogram 1054. The terminal units 1046 to 1048 respectively includeterminal-unit programs 1055 to 1057. The network node units 1041 to 1044include respective communication records for management of encapsulationand decapsulation and filter control records 1041-1 to 1044-1 fordetermining a way of packet selection. Filter control record 1041-1includes multiple filter control records for each terminal 1046 to 1048.In the present case, a packet to be sent by the terminal programs 1055to 1057 has a source port number “5000”. The respective terminal-unitprograms are configured to operate as servers in a client-server model.The ASP site program 1054 is configured to operate as a client in theclient-server model.

[0810] Numeral 1040-1 (in FIG. 232) shows a range of communicationprocedure of within the IP network 1040. An IP packet 1050 (FIG. 231)forwarded from the ASP site program 1054 includes a TCP packet, having asource port number “7100” and destination port number “5000”, to reachthe network node unit 1041 (Step T1 in FIG. 232). Then, a filter controlrecord 1041-1 is used to examine the IP packet 1050. When thedestination port number “5000” is passed, an internal packet is formedand transferred within the IP network to reach the network node unit1042 (Step T2) where a filter control record 1042-1 is used to examinethe internal packet. In case the destination port number “5000” ispassed, an external packet is restored from the internal packet. Therestored external packet 1050 passes over a communication line to reachthe terminal-unit program 1055 (Step T3). When an IP packet is sent fromthe terminal-unit program 1055 (Step T4), a filter control record 1042-1is used in the network node unit 1042 to turn an IP packet selected as asource port number “5000” into an internal packet. The internal packetis transferred within the IP network (Step T5). In the network node unit1041, a filter control record 1041-1 is used to restore an external IPpacket from an internal packet selected as a source port number “5000”.The restored external IP packet reaches the ASP site program 1054 (StepT6).

[0811] Furthermore, the IP packet 1051 forwarded from the ASP siteprogram 1054 (Step T11) contains a TCP packet, having a source portnumber “8100” and destination port number “5000”. The IP packet 1051 isexamined by the use of a filter control record 1041-1 similarly to theforegoing. The internal packet is transferred within the IP network(Step T12). In the network node unit 1043, a filter control record1043-1 is used to examine the internal packet. A restored externalpacket 1051 reaches the terminal-unit program 1056 via a communicationline (Step T13). When an IP packet is sent from the terminal-unitprogram 1056, in the network node unit 1043 a filter control record1043-1 is used to form an internal packet to be transferred. In thenetwork node unit 1041, a filter control record 1041-1 is used and arestored external IP packet reaches the ASP site program 1054 (Steps T14to T16). Furthermore, an IP packet 1052 forwarded from the ASP siteprogram 1054 (Step T21) contains a TCP packet, having a source portnumber “9100” and destination port number “5000”. Similarly to theforegoing, a filter control record 1041-1 is used to examine the IPpacket 1052, thereby forming and transferring an internal packet (StepT22). In the network node unit 1044, a filter control record 1044-1 isused to examine the internal packet. A restored external packet 1052passes over a communication line to reach the terminal-unit program 1057(Step T23). When an IP packet is sent from the terminal-unit program1057, a filter control record 1044-1 and filter control record 1041-1 isused on the principle similar to the foregoing. A restored external IPpacket reaches the ASP site program 1054 (Steps T24 to T26).

[0812] <<LAN Lease Service>>

[0813] In FIG. 233, numeral 1060 is an IP network, numerals 1061 to 1063are LANs on lease, numeral 1064 is a range to cover the LANs on lease1061 to 1063 by a LAN leaser, numeral 1065 is an ASP site, numerals 1066to 1070 are terminal units, numerals 1071 to 1076 are network nodeunits, numerals 1085 to 1089 are LANs, numerals 1080 to 1084 are agathering of communication records as main tables of unit control tablesand various control records as sub-tables, e.g. form of 742-1 to 742-6shown in FIG. 67. In this embodiment, explanation from now on is made,merely as a communication record, a pair of communication records asmain tables and various control records as sub-tables.

[0814] The LANs 1085 and LANs 1087 are Company A's LANs, includingterminal units 1066 and 1068 therein. The Company-A has a LAN 1061leased from a LAN leaser. The LAN 1061 includes various resources foruse by the Company A (servers, database, application programs, domainname servers, data storages, and so on). The terminal unit 1066 isallowed to use the various resources of within the LAN 1061 by way ofcommunication lines (Step 1091 in FIG. 234). Similarly, the terminalunit 1068 is allowed to use various resources of within the LAN 1061 byway of communication lines (Step 1092). For a communication between theterminal unit 1066 and the resources of within the LAN 1061 (Step 1091),used is a communication record 1080 and 1081 in the unit control table.Also, for a communication between the terminal unit 1068 and theresources of within the LAN 1061 (Step 1092), used is a communicationrecord 1082 and 1083 in the unit control table. Because there are noother communication records for communication with the resources ofwithin the LAN 1061 in the network node unit 1074 and other network nodeunits, the Company-A is allowed to exclusively use the LAN 1061. It issatisfactory for the Company-A to possess a terminal units 1066 and 1068for access to the LAN 1061. Thus, there is a merit of unnecessity ofexpertise technicians who maintain and manage the servers of the LAN1061 and of rooms for accommodating the resources of the LAN 1061.

[0815] <<Joint Utilization of ASP Site>>

[0816] The ASP site 1065 can afford to include therein variousapplication servers, WEB servers, database and data storages. 1086 is aCompany-X's LAN, including a terminal unit 1067. Numeral 1088 is aCompany-Y's LAN, including a terminal unit 1069. Numeral 1089 is aCompany-Z's LAN, including a terminal unit 1070.

[0817] Company X can send and receive an IP packet to and from the ASPsite 1065, to use the internal resources of the ASP site 1065 (Step 1093in FIG. 234). Company Y can send and receive an IP packet to and fromthe ASP site 1065 and IP packet, to use the internal resources of theASP site 1065 (Step 1094). Company Z can send and receive an IP packetto and from the ASP site 1065, to use the internal resources of the ASPsite 1065 (Step 1095). Namely, Company X to Company Z can jointly usethe ASP site 1065. Because there are no other communication records forcommunication with the ASP site 1065 in the other network node units,the three of Company X to Company Z can use the ASP site for their ownpurposes. In the case that Company X to Company Z are banks,-suchapplication programs as commonly used by the banks can be set up in theASP site and utilized in a joint fashion. Where Company X to Company Zare insurers, such application programs as commonly used by the insurerscan be installed in the ASP site 1065 and utilized. By considerationreplacing Company X to Company Z with business circles, it is possibleto limitlessly list up, e.g. automobile industry, architecture industryand travel industry.

[0818] <<ASP Provision of LAN Under Lease>>

[0819] Company A leases a LAN 1061 so that the third party can utilize,as servers, the various resources of the LAN 1061 from the Company-A'sterminal units 1066 to 1068. Next, in order for the respective terminalunits 1067, 1069, 1070 of Company X to Company Z to utilize as serversthe resources of within -the LAN 1061, the common carrier operating theIP network 1060 is asked to set up communication records in the relatednetwork node units. Thereupon, the company A can provide ASP services toCompany X to Company Z by leasing the LAN 1061, i.e. without possessingthe LAN of the ASP service.

[0820] <<Summary>>

[0821] The IP network includes two or more network node units. Theprograms in the ASP site send an external packet to the terminals of oneor more utilizers. The external packet is inputted at a logic terminalto a source-sided network node unit. From a selected external packet, aninternal packet is formed so that the internal packet is transferredwithin the communication network. Concerning the internal packet, in adestination-sided network node unit, an external packet is restored froma selected internal packet and forwarded onto an external communicationline 2 in the IP network. In at least one of upon forming an internalpacket and upon restoring an external IP packet, at least one of aprotocol and a port number of the external packet is to be used. Thus,an IP packet can be send from the utilizer's terminal unit back to theprogram in the ASP site. The programs in the ASP site operate as clientsof a client-server model. The program on the utilizer's terminal unit isoperated as a server of the client -server model, and that enhancescommunication security between the ASP site and terminals.

[0822] By operating a selected packet as an external IP packet, furtherthe programs in the ASP site as a client of the client-server model andthe program on the utilizer's terminal unit as a server of theclient-server model, security can improved for the server or program ofwithin the ASP site. For the network node unit within the IP network,there are a case to use its encapsulation function and a case to use anaddress inspection function using the registration information of withinthe network node unit. Both are possible to carry out.

[0823] Furthermore, in case Company A leases a LAN in a manner passingthrough the IP network, an IP packet can be communicated between theCompany-A's terminal unit and the resources within the leased LAN.Accordingly, in order to set up a communication record in a unit controltable of within the network node unit of the IP network and disableIP-packet communication between the terminal unit other than theCompany-A's terminal and the resources within the leased LAN, a LANleaser can lease a LAN by not setting a communication record in a unitcontrol table of every network node unit in the IP network. Meanwhile,Company X to Company Z set up a communication record to the unit controltable of a network node unit within the IP network in order tocommunicate IP packets with the ASP site. The other than the Company Xto Company Z are not set up, in every network node unit, with acommunication record of enabling communication of IP packets with theASP site. Thus, two or more companies can jointly utilize the ASP site.Meanwhile, the ASP can offer ASP services using the LAN under lease.

[0824] <<Encapsulation and Address-Inspection Functions>>

[0825] The network node units within the IP network are used in theirencapsulation functions, to turn an external IP packet into an internalpacket so that the packet is transferred within the communicationnetwork and decapsulated, in a destination-sided network node unit, torestore an external IP packet. The network node units carry out one ormore of packet priority control, multicast control and signaturefunction, thereby making possible to further improve the informationsecurity on the communication network of IP network. The enables secureimplementation of the LAN lease service and the joint utilization of ASPsite. Meanwhile, the network node units within the IP network do not usean encapsulation function. A packet, selected by an address inspectionusing an in-network-node-unit registration information explained inEmbodiment 7 (see FIG. 222), is transferred within the communicationnetwork. At this time, the network node unit conducts an addressinspection and one or more of packet priority control, multicast controland signature function, thereby making possible to further improve theinformation security on the communication network. That enables secureimplementation of the LAN lease service and the joint utilization of ASPsite.

[0826] 10. Embodiment 10 for Transmitting Multicast Data to MobileTerminal Unit:

[0827]FIG. 235 shows an IP network 300-1 for distributing multicastdata, which is a figure changing a part of FIG. 37 (Embodiment 3)explaining multicast data distribution. In preparation for explainingFIG. 235, summarization is made to the multicast data distribution ofFIG. 37.

[0828]FIG. 37 shows a flow of multicast data. When an IP packet is sentfrom the terminal unit 320, the IP packet reaches the network node unit311 and turned into an internal packet, thus being transferred to therouters 317 and 319. The internal packet transferred to the router 317is transferred to the network node unit 312 and router 318. The internalpacket transferred to the network node unit 312 is restored to anexternal IP packet and transferred to the terminal unit 322. Theinternal packet reaching the router 318 is transferred to the networknode units 313 and 314. The internal packet reaching the network nodeunit 313 is restored to an external IP packet to reach the terminal unit323. The internal packet reaching the network node unit 314 is restoredto an external IP packet to reach the terminal unit 325. On the otherhand, the internal packet, forwarded from the network node unit 311 toreach the router 319, is transferred to reach the network node unit 315where it is restored into an external IP packet and reaches the terminalunit 327. In encapsulation of from an external IP packet into aninternal packet and decapsulation of from an internal packet into anexternal IP packet, used is an address management table in the networknode unit. The terminal units 320 to 327, having one destination-sidednetwork node unit, are referred to as fixed terminals. These when usedas telephone sets are referred to as fixed telephone sets. Incidentally,the terminal unit used in mobile communication referred later or thelike is referred also as a mobile terminal unit. This when used as atelephone set is referred also to as a mobile phone. The mobile phonehas a telephone number capable of identifying the mobile terminal.

[0829] Next, explanation is made on a flow of multicast data by the IPnetwork 300-1 (FIG. 235). In the IP network 300-1, there are networknode units 311 to 315. The terminal units 320 to 327 are connected tothe network node units via communication lines and multicast data istransmitted from the terminal unit 320, which is similar to FIG. 37. Thedifference from FIG. 37 lies in that the terminal units 321, 324, 326are to receive multicast data. In the IP network 300-1, the addressmanagement tables of the network node units 311 to 315 respectivelyinclude records 331-1 to 335-1 (FIG. 236) defining multicast deliveryroutes. The router 317 includes a multicast table 337-1 (in FIG. 237) asa route table element defining internal-IP-packet delivery destinations.The router 318 includes a multicast table 338-1 as a route tableelement, while the router 319 includes a multicast table 339-1 as aroute table element.

[0830] In order to add receiving terminal units 321, 324 and 326, thereare modifications in the records of address management tables of withinthe network node units and the records in route tables in the routers.The multicast record (first line) of the address management table 331(in FIG. 40) within the network node unit 311 is added by a logic outputinterface “G00” to the terminal unit 321 and changed into a record “I01,E01, M1, IM1, (G02′, G03, G00), 0” and further into a record “IM1, M1,E01, I01, G00, F02” as shown in 331-1 (in FIG. 236). “G00” shows aninternal logic output interface of the network node unit 311, which is afolded line in the meaning that the output of the network node unit 311is returned to an input.

[0831] The multicast record (first line) of the address management table332 (in FIG. 40) in the network node unit 312 is similar to the record332-1. The multicast record (second line) of the address managementtable 333 (in FIG. 42) in the network node unit 313 is added by a logicoutput interface “F11” to the terminal unit 324 and changed into arecord “IM1, M1, E01, I01, G31, (F10, F11) ”. The multicast record(first line) of the address management table 334 (in FIG. 42) in thenetwork node unit 314 is similar to the record 334-1. The multicastrecord (second line) of the address management table 335 (in FIG. 42) inthe network node unit 315 is added by a logic output interface “F17” tothe terminal unit 326 and changed into a record 335-1 “IM1, M1, E01,I01, G31, (F17, F18) ”.

[0832] The address management tables described in Embodiment 3 areincluded in the function of the unit management tables disclosed inEmbodiment 7, which will be explained with reference to FIG. 238. In332-1 x (FIG. 238), on the first line (the upper) is shown acommunication record 738 (in FIG. 62) while on the second line (thelower) is shown a in-address-management-table record 332-1 (in FIG. 236)changed in item order, wherein correspondence can be given between “ISA”and “IMI”, “IRA” and “101”, “NSA” and “M1”, “NDA” and “E01”, “MSA” and“one”, “MDA” and “one”, IFI” and “G04”, and “IFE” and “F04”. Namely,these are items used for the same purpose. Herein, “one” refers to255.255.255.255 (when in IPv4).

[0833]FIG. 239 shows a form that media routers 320M to 327M are arrangedbetween the network node units of within the IP network 300-1 and theterminal units at the outside of the IP network 300-1. The media routeraccommodates a plurality of terminal units having an IP-packettransmitting/receiving function to have a function of connection to anetwork node unit. This, in the invention, is carried out as 903-1 (FIG.108), for example. Explaining it with reference to FIG. 239, an IPpacket containing multicast data is sent from the terminal unit 320 toreach the network unit 311 via the media router 320M. In the networknode unit 311, an internal packet is formed by the use of a first-linedrecord 331-1 “I01, E01, M1, IM1, (G02, G03, G00), 0” of the addressmanagement table. The internal packet is transferred to the router 317connected to a communication line designated by the record item “G02”,to the router 319 connected to a communication line designated by therecord item “G03”, and to the network node unit 311 connected to acommunication line designated by the item “G00” (folded back).

[0834] The internal packet transferred to the router 317 is used by anitem “G11” and item “G12” of in the route table 337-1 and transferred tothe router 318 connected to a communication line designated by “G12” andto the network node unit 312 connected to a communication linedesignated by “G11”. The internal packet transferred to the router 318is used by an item “G27” and item “G28” of in the route table 338-1 andtransferred to the network node unit 313 connected to a communicationline designated by “G27” and to the network node unit 314 connected to acommunication line designated by “G28”. On the other hand, the internalpacket transferred to the router 319 is used by an item “G22” of in theroute table 339-1 and transferred to the network node unit 315 connectedto a communication line designated by “G22”.

[0835] The internal packet reaching the network node unit 311 is used bya record 331-1 “IM1, M1, E01, I01, G00, F02” on a second line of theaddress management table to restore an external packet. The restoredexternal packet is transferred to the media router 321M connected to acommunication line designated by the record item “F02”. The subsequentis similarly done. The internal packet reaching the network node unit312 to 315 is used by a record “IM1, M1, E01, I01, . . . , . . . ” asthe address management table record 332-1 to 335-1 to restore anexternal packet. The restored external packet is transferred to themedia router 322M to 327M connected to a communication line designatedby the record item “F04”, “F10”, F11”, . . . “F18”.

[0836] An IP network 300-2 (FIG. 240) is set up with address managementtable records for multicast distribution in the network node units 311to 315 and route tables for multicast branching in the routers 317 to318, similarly to the IP network 300-1 (FIG. 239). Furthermore, themedia router 321M (FIG. 239) is replaced with a radio base point 321B.Furthermore, the media routers 323M to 327M (FIG. 239) are respectivelyreplaced with radio base points 323B to 327B (FIG. 240). The radio basepoint 321B and the radio base points 323B to 327B are installed withinthe IP network 300-2. The arrow on a communication-line shows amulticast distribution route. The radio point has a function toaccommodate a plurality of mobile terminal units, for connection to anetwork node unit, which in the invention is embodied, e.g. as 902-3(FIG. 108). The multicast distribution route set up within the IPnetwork 300-2 is the same as the multicast distribution route set upwithin the IP network 300-1. Accordingly, a multicast IP packetforwarded from the terminal unit 320 passes the media router 320M to beinputted to the IP network 300-2 to reach a fixed terminal unit 322 ANDmobile terminal units 321B, 323B to 327B by way of multicastdistribution routes by way of multicast distribution routes of withinthe IP network 300-2.

[0837] An IP network 1100 (FIG. 241) is an IP network formed by addingservers and routers to the IP network 300-2. The IP network 1100 and thenetwork 300-2 have internal resources in correspondence, as follows.Network node units 1101 to 1105 (FIG. 241) respectively correspond tothe network node units 311 to 315 (FIG. 240). Routers 1107, 1108, 1109(FIG. 241) respectively correspond to the routers 317, 318, 319 (FIG.240). The connection relationship of communication lines between thenetwork node units and the routers also has a one-to-one correspondence.Fixed terminal units 1120 and 1122 (FIG. 241) respectively correspond tothe fixed terminal units 320 and 322 (FIG. 240). Mobile terminal units1121, 1123 to 1127 respectively correspond to the mobile terminal units321B, 323B to 327B.

[0838] The arrow on a communication line within the IP network 1100shows a multicast distribution route. The multicast distribution routewithin the IP network 1100 is set up the same as the multicastdistribution route of within the IP network 300-2. Accordingly, amulticast IP packet forwarded from the terminal unit 1120 passes themedia router 1110 to be inputted to the IP network 1100, reaching afixed terminal unit 1122 or mobile terminal units 1121, 1123 to 1127 byway of multicast distribution routes within the IP network 1100.

[0839] In FIG. 241, the network node units 1101 to 1105 are respectivelyconnected with terminal-unit control sections 1131 to 1135. Meanwhile,the terminal-unit control section 1131 to 1135 is set up, therein, witha telephone number server 1131-5 to 1135-5, a telephone managementserver 1131-4 to 1135-4, and a table management server 1131-3 to 1135-3.Numeral 1106 is a router, 1136 is a superior telephone number server,numeral 1137 is a user service server, and numerals 1138 and 1139 aremulticast authentication servers for confirming the correctness of themulticast receiving terminals of the mobile terminal units (Mauthentication servers). The terminal-unit control section 1131,telephone management server 1131-4, telephone number server 1131-5 andsuperior telephone number server 1136 shoulder the same function as theterminal-unit control section 914-1, telephone management server 906-4,telephone number server 906-5 and superior telephone number server 995shown in FIG. 108. The function of the M authentication server 1138,1139 is explained in this embodiment. The terminal-unit control sections1131 to 1135 are connected via communication lines. The communicationlines allow to transfer an internal packet or the like containing aline-connection control message for call control.

[0840] It is possible to provide a correspondence between thecommunication elements described in FIG. 108 and the communicationelements described in FIG. 241, for example, as in the following. Thetelephone set 905-1 (in FIG. 108) can be made corresponding to a fixedtelephone set 1120 (in FIG. 241), the media router 903-1 is to a mediarouter 1110, the network node unit 906-1 is to a network node unit 1101,the terminal-unit control section 914-1 is to a terminal-unit controlsection 1131, the communication line 912-1 to a communication line 1144,the connection control section 914-4 to a terminal-unit control section1134, the network node unit 909-1 is to a network node unit 1104, theradio base point 902-4 is to a radio base point 1115, and the mobilephone 905-8 is to a mobile phone 1125.

[0841] Furthermore, a control communication line connecting from aterminal-unit control section 1131 (FIG. 241) to a communication line1144, router 1141 and terminal-unit control section 1134 can be madecorresponding to the control communication line connecting from theterminal-unit control section 914-1 (FIG. 108) to the communication line912-1, router 911-1, router 911-2, router 911-3 and terminal-unitcontrol section 914-4. To the control communication line is to betransferred a packet or the like storing a line-connection controlmessage based on a common channel signaling system. Furthermore, a mediacommunication line connecting a network node unit 1101 (FIG. 241),communication line 1145, router 1107, router 1108 and network node unit1104 can be made corresponding to the media communication lineconnecting the network node unit 906-1 (FIG. 108), communication line913-1, router 911-4, router 911-5, router 911-6 and network node unit909-1. To the media communication line is to be transferred telephonevoice and image data or multicast data including voice and image data,besides text data.

[0842] From the fact that telephone communication can be made betweenthe fixed telephone set 905-1 and the mobile phone 905-8 by theline-connection control applying a common channel signaling system tothe IP network as explained in FIG. 183, by the correspondence betweenthe communication elements described in FIG. 108 and the communicationelements described in FIG. 241, telephone communication can be madebetween the fixed telephone set 1120 and the mobile phone 1125 accordingto a line-connection control applying a common channel signaling systemto the IP network. By a method similar to the above, telephonecommunication can be made, for example, between the mobile phone 1121and the mobile phone 1124. Furthermore, telephone communication ispossible between the fixed telephone set 1122 and the fixed telephoneset 1120.

[0843] <<Multicast Receive Request and Reception End>>

[0844] Explanation is made on a case that the mobile terminal unit 1121transmits radio wave information including a multicast receive requestthat is unexpectedly connected to a radio base point 1111 via a radiocommunication line 111-1 (FIG. 241). The radio base point 1111 firstexchanges information with the mobile terminal unit 1121 to confirm acommunicatability through a radio communication path (Step V1 in FIG.242). The confirmation procedure is made in the communication level 1 or2. When a communicatability is confirmed, the mobile terminal unit 1121transmits a multicast receive request (Step V2). The multicast receiverequest information includes a telephone number “TN3” to be used by themobile terminal unit 1121, terminal unit authentication information“PID3” and multicast reception-terminal-unit authentication information“PID-M” (password or the like). Incidentally, the multicastreception-terminal-unit authentication information can use the terminalauthentication information “PID3” set in the telephone numberregistration of a mobile phone in Communication Case 2 in Embodiment 8and terminal authentication information “PID-M”.

[0845] The radio base point 1111 forms an external packet 1160 (FIG.243) containing a telephone number “TN3” included in terminalauthentication information “PID3”, external IP address “EB1” of themobile terminal unit 1121 and second terminal-unit authenticationinformation “PID-M”, and sends it toward a multicast authenticationserver 1138 (external IP address “WA9”) Herein, the external packet 1160has a source external IP address “EB1” and a destination external IPaddress “WA9”. The external packet 1160 reaches the network node unit1101 (Step V3), where a third-lined record “IB1, EB1, WA9, IWA9, . . . ”of an address management table 1101-1 in a network node unit 1101 (FIG.245) is used to form an internal packet 1161 (FIG. 244). The internalpacket 1161 is sent to the multicast authentication server 1138 (StepV4). The multicast authentication server 1138 receives the internalpacket 1161 and acquires, from the received internal packet, a telephonenumber “TN3”, external IP address “EB1”, internal IP address “IB1” andmulticast authentication terminal-unit authentication information“PID-M” and holds them therein (Step V5). An internal packet containinga telephone number “TN3” is formed and sent to the telephone numberserver 1131-5 (Step V6). The telephone number server 1131-5 notifies theacquired telephone number “TN3”, together with an identification symbolof telephone number server 1131-5, to a superior telephone number server1136 (Step V7). The superior telephone number server 1136 extractsmulticast authentication terminal-unit authentication information“PID-M” from the telephone number “TN3” held therein, and notifies it tothe authentication server 1138 (Step V9) via the telephone number server1131-5 (Step V8). The authentication server 1138 confirms whether thereceived information agrees with the telephone number “TN3” received inthe step V4 and multicast authentication terminal-unit authenticationinformation “PID-M”. In the case of agreement (pass), the processproceeds to the following. Where in disagreement, the subsequentprocedure is suspended.

[0846] The multicast authentication server 1138 notifies a result ofauthentication (pass, failure) to the mobile terminal unit 1121 via thenetwork node unit 1101 and radio base point 1111 (Steps V11 to V13). Themobile terminal unit 1121 can reply to the authentication resultnotification (Step V13 x, option). Furthermore, in an acceptance case,the authentication server 1138 asks the table management server 1131-3(Step V15) to rewrite the second-lined record “IM1, M1, E01, I01, G00,0” of a address management table record 1101-1 (FIG. 245) of in thenetwork node unit 1101 into a record “IM1, M1, E01, I01, G00, F02” shownin 1101-2 (Step V16). Namely, the sixth item “0” is rewritten to “F02”.Thereupon, an external IP packet storing multicast data forwarded fromthe fixed terminal unit 1120 passes the media router 1110 (Step V21) toreach the network node unit 1101 (Step V22), where a first-lined record“I01, E01, M1, IM1, (G02, G03, G00), 0” of the address management table1101-1 is used. The internal packet moved back by an item “G00” returnsto the network node unit 1101 (Step V23). Applied by a record 1101 “IM1,M1, E01, I01, G00, F02” of the network node unit 1101-2, an IP packetstoring multicast data to be forwarded at the item “F02” is forwardedonto a communication line 1111-2 (FIG. 241) designated by “F02” (StepV24). Next, it passes the radio base point 111 to reach the mobileterminal unit 1121 (Step V25). Meanwhile, the multicast authenticationserver 1138 notifies a multicast data transmission start to the userservice server 1137 (Step V17). The user service server 1137 can use areport of multicast data reception as fee-charge information to theterminal unit 1121 (Step V18, option).

[0847] Multicast data reception end procedure is made as in thefollowing order. A multicast data reception end request is forwardedfrom the mobile terminal unit 1121 to the radio base point 1111 (StepV30). When the radio base point 1111 forwards an external IP packetcontaining a multicast data reception end request, the external IPpacket reaches the network node unit 1101 (Step V31) and encapsulatedinto a multicast data reception end request internal packet. Themulticast data reception end request internal packet is delivered to themulticast authentication server 1138 (Step V32). The external IP packetcontaining a multicast data reception end request contains the similarcontent to the external IP packet 1160 (FIG. 243), i.e. a telephonenumber “TN3”, external address “EB1”, terminal-unit authenticationinformation and so on. The internal IP packet containing a multicastdata reception end request is similar to the internal IP packet 1161.The multicast authentication server 1138, receiving the internal IPpacket containing a multicast data reception end request, asks the tablemanagement server 1131-3 (Step V33) to rewrite the content shown in therecord 1101-2 of the address management table in the network node unit1101 to the content shown in 1101-3 (Step V34) to prevent the IP packercontaining multicast data from being transmitted to the radio base point1111 and report the user service server 1137 of stopping multicast datadistribution (Step V35). The user service server 1137 can use amulticast data service reception report as a fee-charge information ontothe terminal unit 1121 (Step V36, option). Meanwhile, the authenticationserver 1138 can report a result of multicast data distribution stop tothe radio base point 111 (Steps V37 x, V38 x, option).

[0848] <<Multicast Data Transmission from Mobile Terminal Unit>>

[0849] In place of transmitting an external packet containing multicastdata from the fixed terminal unit 1120, multicast data can betransmitted from the mobile terminal unit 1121 to the radio base point1111 via a radio communication path 1111-1 so that an external packetcontaining the received multicast data is formed and transmitted fromthe radio base point 1111 via a communication path 1111-2 to the networknode unit 1101, being transferred in the IP network 1100 and distributedto the fixed terminal unit 1122 and mobile terminal units 1123 to 1127.Namely, it is possible to distribute the multicast data having an originof the mobile terminal unit 1121. At this time, the records, in thenetwork node unit and routers, defining a multicast distributiondestination are set and used based on the principle explained usingFIGS. 235 and 236.

[0850] <<Free-of-Charge Multicast Service>>

[0851] In the implementation of multicast service, free-of-chargemulticast service can be realized by omitting the authenticationprocedure on a multicast data receiving terminal and the procedureconcerning fee charge on a user service server. Namely, the Steps V17,V18, V35 and V36 are not executed in FIG. 242.

[0852] <<Summary>>

[0853] The IP network previously sets up a record for multicast datadistribution in address management tables in the network node units anda record defining a multicast distribution destination in route tablesof within the routers, to transmit an external packet containingmulticast data from a fixed terminal unit. The external packet reaches asource-sided network node unit, and turns into an internal packetaccording to the designation of a record of the address managementtable, being transferred onto one or more internal communication lines.The transferred internal packet, when passing a router, follows anin-router multicast record. The internal packet arrives one or morereception-sided network node units on a side close to a receptionterminal. In the reception-sided network node unit, an external packetis restored from the internal packet. The restored external packetcontaining multicast data, as a first case, can be transferred from thereception-sided network node unit to a fixed terminal unit via anexternal communication line and media router. As a second case, it canbe transferred from the reception-sided network node unit to the radiobase point via an external communication line, and, in the radio basepoint, delivered to a mobile terminal unit via a radio communicationline. In place of transmitting multicast data from a fixed terminalunit, multicast data can be transmitted from a mobile terminal unit to aradio base point via a radio communication line so that an externalpacket containing the received multicast data is formed and transmittedfrom the radio base point to a network node unit via a communicationpath to be transferred within the IP network 1100, thereby distributingmulticast data.

[0854] In the case that the mobile terminal unit issues a multicastreceive request containing at least multicast receiving terminal-unitauthentication information, the receive request makes a request to amulticast authentication server. When the multicast authenticationserver, when the mobile terminal unit is allowed for multicastreception, asks the table management server to rewrite a multicastdistribution record of the address management table in a network nodeunit the mobile terminal is to connect, thereby making the mobileterminal unit receivable. Namely, the multicast data is rewritten andthe multicast data is transferred to a reception-requesting mobileterminal unit according to record designation. The multicastauthentication server notifies the user service server of multicast datadelivery being possible, thus making it possible to use it as fee-chargeinformation. When a multicast data reception end request is issued fromthe mobile terminal unit, the multicast authentication server knows theend request. The multicast authentication server asks the tablemanagement server to rewrite an address management table record in thenetwork node unit, to stop multicast data transfer and report the stopof distributing user service server multicast data. Free multicastservices can be implemented.

[0855] According to the present invention, because communication is madewith another telephone set or voice image unit by way of an IP networkand mobile communication network, realized is a terminal-to-terminalcommunication connection control method for telephone communication orvoice image communication; realized is a terminal-to-terminalcommunication connection control method by establishing a TCPcommunication path between a source-sided telephone management serverand a destination-sided telephone management server and thenestablishing a communication path for terminal-to-terminalcommunication, and thereafter carrying out a voice image communicationbetween the two voice image units via the IP network; realized isresolving the method for TV conference with IP multicast by setting acommunication record for multicast to an address management table in anetwork node unit and setting a route table for multicast to transmit avoice moving image by the use of a multicast address; realized isresolving the method for configuring a gateway for connection between anIP network based on the common channel signaling system and a PSTNthrough installing a relay gateway within an IP network in order fortelephone communication of telephone set-IP network-PSTN-telephone set;realized is resolving the method for structuring an IP network bysetting an entire or part of an external address in an address area ofan internal packet due to a method of setting to an inside of anexternal IP packet upon IP packet encapsulation; realized is resolvingthe method for structuring an IP network by a method of setting anentire or part of an external address in an address area of an internalframe; realized is resolving the method for structuring an security IPnetwork by carrying out a method to separate an IP network into aplurality of internal IP networks by the use of a packet filter, apriority control function, a multicast recipient address conversionfunction or a port number; realized is a method for carrying out fixedtelephone communication and-mobile telephone communication on the sameIP network based on the common channel signaling system by the use of aCIC management table including a management function of a UNI on theterminal unit side; realized is an IP network capable of carrying outsecurity ASP by selecting an IP address, port number or protocol kind ofan IP packet communicated between an ASP server and a user program by anetwork node unit; provided is IP packet exchange service (Intranet,Extranet) and fixed telephone service and mobile phone service, withoutdistinction, by IP networks based on the same principle and realized isa multicast data method without distinction between the mobile terminalunit and the fixed terminal unit; and realized is resolving the methodfor registering and changing a whereabouts position of a telephone setby registering a mobile phone in a mobile communication networkcomprising an IP network in order to carry out mobile phonecommunication.

[0856] of the eighth embodiment of the invention.

What is claimed is:
 1. A terminal-to-terminal communication connectioncontrol method using an IP network characterized in that: in order for amobile phone set to have a telephone communication with a fixedtelephone set by way of a mobile communication network and an IPnetwork, the mobile communication network carries out a line connectioncontrol based on a common channel signaling system; the IP networkestablishing a communication path by carrying out a line connectioncontrol applying the common channel signaling system to the IP networkthereby effecting a telephone communication.
 2. A terminal-to-terminalcommunication connection control method using an IP networkcharacterized in that: in order for a voice image unit 1 to have a voiceimage communication with a voice image unit 2 by way of a mobilecommunication network and an IP network, the mobile communicationnetwork carries out a line connection control based on a common channelsignaling system; the IP network establishing a communication path by aline connection control applying the common channel signaling system tothe IP network, and thereafter carrying out a control procedure forsetting up a voice image communication path between the voice imageunits 1 and 2 to effect a voice image communication between the voiceimage units 1 and 2; when the voice image communication ends, the voiceimage units 1 and 2 carrying out a control procedure for closing thevoice image communication path; the mobile communication networkreleasing according to a line connection control based on the commonchannel signaling system; the IP network releasing the communicationpath according to a line connection control applying the common channelsignaling system to the IP network.
 3. A terminal-to-terminalcommunication connection control method using an IP networkcharacterized by: establishing previously a TCP communication pathbetween a source-sided telephone management server and adestination-sided telephone management server; transmitting andreceiving circuit connection control messages IAM, ACM, CPG, ANM toestablish a media communication path for terminal-to-terminalcommunication, and thereafter communicating multimedia data between twoterminal units; communicating line connection control messages REL, RLCbetween the source-sided telephone management server and thedestination-sided telephone management server to release the mediacommunication path thereby releasing the TCP communication path.
 4. Aterminal-to-terminal communication connection control method using an IPnetwork characterized by: establishing a TCP communication path betweena source-sided telephone management server and a destination-sidedtelephone management server; thereafter transmitting and receivingcircuit connection control messages IAM, ACM, CPG, ANM to establish amedia communication path for terminal-to-terminal communication, andthereafter releasing the TCP communication path; communicatingmultimedia data between two terminal units; when the communication ofthe multimedia data ends, establishing a new TCP communication pathbetween the source-sided telephone management server and thedestination-sided telephone management server; thereafter communicatingline connection control messages REL, RLC to release the mediacommunication path and release the new TCP communication path.
 5. A TVconference communication method using an IP network including one ormore network node unit characterized by: setting an address managementtable in a network node unit, and setting a route table for multicast IPpacket transfer in a router of within an IP network; a sender 1 sendinga multimedia data by using a multicast address M1, one or more receiversreceiving the multimedia data by using the multicast address M1; asender 2 sending a multimedia data by using a multicast address M2, oneor more receivers receiving the multimedia data by using the multicastaddress M2; an IP packet being encapsulated by the address managementtable and transferred within the IP network to use the multicasttransmission/reception function.
 6. An IP network including one or morenetwork node unit characterized in that: an external IP packet beingconverted into an internal packet in an input-sided network node unitand transferred within an IP network; the external IP packet being to berestored from the internal packet in an output-sided network node unit;under the control of a record of an address management table of withinthe input-sided network node unit, an entire or part of an externaladdress set in the external IP packet being to be set to an address areaof the internal packet.
 7. An IP network according to claim 6, whereinthe record of the address management table can be set in plurality, adestination of transfer of the internal packet being to be changed bychanging the external destination address of in the external IP packet.8. A network node unit characterized by: inputting an external IP packetand converted into an internal packet and outputted by setting an entireor part of an external address to an address area of an internal packetunder the control of a record of an address management table of within anetwork node unit, the internal packet being input to restore and outputthe external IP packet.
 9. A network node unit according to claim 8,wherein the record in the address management table can be set inplurality, a destination internal address of the internal packet beingto be changed by changing an external destination address in theexternal IP packet.
 10. An IP network including one or more network nodeunit characterized in that: an external IP packet is converted into aninternal packet in an input-sided network node unit and transferredwithin an IP network; the external IP packet being to be restored fromthe internal packet in an output-sided network node unit; an internalframe containing a destination internal address but not containing asource internal address; under the control of a record of an addressmanagement table of within the input-sided network node unit, an entireor part of an external address set in the external IP packet being to beset to an address area of the internal packet.
 11. An IP networkaccording to claim 10, wherein the record in the address managementtable can be set in plurality, a destination of transfer of the internalframe being to be changed by changing the external destination addressof in the external IP packet.
 12. A network node unit characterized by:inputting an external IP packet and converted into an internal packetand outputted by setting an entire or part of an external address to anaddress area of an internal packet under the control of a record of anaddress management table of within a network node unit; the internalframe containing a destination internal address but not containing asource internal address; the internal packet being inputted to restoreand output the external IP packet.
 13. A network node unit according toclaim 12, wherein the record in the address management table can be setin plurality, a destination internal address of the internal frame beingto be changed by changing the external destination address of in theexternal IP packet.
 14. An IP network characterized in that: the IPnetwork includes two or more network node units; an external packetturning into an internal packet under the control of a unit controltable of the network node unit; the internal packet being transferredwithin the IP network; the internal packet being restored as an externalpacket in a destination-sided network node unit; the unit control tableincluding address information related, at least, to the external packetand internal packet; reference being made to a protocol kind of in theexternal packet to turn a selected one of the external packet into aninternal packet; reference being made to a protocol kind of in theexternal packet in the internal packet to restore a selected one of theinternal packet into an external packet.
 15. An IP network characterizedin that: the IP network includes one or more network node unit; anexternal packet is inputted from a logic terminal on an externalcommunication line; by defining three sets of logic terminalidentification information on an inputted source side, a source externalIP address and destination external IP address of in the externalpacket, a destination internal address as a destination of transfer ofthe internal packet being defined under the control of a unit controltable of within a source-sided network node unit; the internal packetbeing transferred within an IP network and restored into an externalpacket in a destination-sided network node unit; reference being made toa protocol kind of in the external packet to turn a selected externalpacket into an internal packet; reference being made to a protocol kindof in the external packet in the internal packet to turn a selectedinternal packet-into an external packet.
 16. An IP network characterizedin that: the IP network includes one or more network node unit; anexternal packet is inputted from a logic terminal on an externalcommunication line; by defining three sets of logic terminalidentification information on a source side, a source external IPaddress and destination external IP address in the external packet, aninternal communication line for internal packet transfer being definedbetween source-sided and destination-sided network node units under thecontrol of unit control tables of within source-sided anddestination-sided network node units and a path table of a relay unit;the internal packet being transferred within a communication network andrestored into an external packet in a destination-sided network nodeunit; reference being made to a protocol kind of in the external packetto turn a selected external packet into an internal packet; referencebeing made to a protocol kind of in the external packet in the internalpacket to restore a selected internal packet into an external packet.17. An IP network according to claim 15 or 16, wherein two sets of theinputted source-sided logic terminal identifying information and thedestination external IP address of in the external packet are usedwithout using the source external IP address in the external packet. 18.An Ip network characterized in that: the IP network includes two or morenetwork node units; an external packet turning into an internal packetunder the control of a unit control table of the network node unit; theinternal packet being transferred within the IP network; the internalpacket being restored as the external packet under the control of theunit control table of the network node unit; the unit control tableincluding address information related, at least, to the external packetand internal packet; when the internal packet is formed, reference beingmade to a port number in the external packet to turn a selected externalpacket into an internal packet or reference being made to a port numberin the external packet in the internal packet to enable restoration ofan external packet from a selected internal packet.
 19. An IP networkincluding one or more network node unit characterized in that: anexternal packet is inputted from a logic terminal on an externalcommunication line; by defining three sets of logic terminalidentification information on an inputted source side, a source externalIP address and destination external IP address in the external packet, adestination internal address as a destination of transfer of theinternal packet being defined under the control of a unit control tableof within a source-sided network node unit; the internal packet beingtransferred within the IP network; when the internal packet is formed,reference being made to a port number in the external packet to turn aselected external packet into the internal packet or reference beingmade to a port number in the external packet in the internal packet torestore the external packet from a selected internal packet.
 20. An IPnetwork including one or more network node unit characterized in that:an external packet is inputted from a logic terminal on an externalcommunication line; by defining three sets of logic terminalidentification information on a source side, a source external IPaddress and destination external IP address in the external packet, aninternal communication line for internal packet transfer being definedbetween source-sided and destination-sided network node units under thecontrol of unit control tables of within source-sided anddestination-sided network node units and a control table of a relayunit; when the internal packet is formed, reference being made to a portnumber in the external packet to turn a selected external packet intothe internal packet or reference being made to a port number in theexternal packet in the internal packet to restore the external packetfrom a selected internal packet.
 21. An IP network according to claim 19or 20, wherein two sets of the inputted source-sided logic terminalidentifying information and the destination external IP address of inthe external packet are used without using the source external IPaddress in the external packet.
 22. An IP network according to claim 14or 18, wherein separated into a plurality of internal IP networks by amethod to transfer the internal packet into a different IP networkaccording to a port number value in the external IP packet.
 23. A methodfor separating, for an IP network according to claim 14 or 18, the IPcommunication network into a plurality of internal IP communicationnetworks by a method to transfer the internal packet into a different IPnetwork according to a port number value in the external IP packet. 24.A communication network characterized in that: a communication networkincludes two or more network node units; an external Ether frame turninginto an internal packet under the control of a unit control table of thenetwork node unit; the internal packet being transferred within thecommunication network; the internal packet being restored as theexternal Ether Frame under the control of a unit control table of thenetwork node unit; the unit control table including address informationrelated, at least, to the external IP packet and internal packet in theEther frame; reference being made to a protocol kind of in the externalpacket to turn a selected external packet into the internal packet orreference being made to a protocol kind of in the external packet in theinternal packet to restore a selected internal packet into the externalpacket.
 25. A communication network including one or more network nodeunit characterized in that: an external Ether frame is inputted from alogic terminal on an external communication line; by defining three setsof logic terminal identification information on an inputted source side,a source external IP address and destination external IP address in theexternal IP packet in the external Ether frame, an internalcommunication line for internal packet transfer being defined betweenthe source-sided and destination-sided network node units under thecontrol of unit control tables of within the source-sided anddestination-sided network node units and a control table of a relayunit; reference being made to a protocol kind of in the external packetto turn a selected external packet into the internal packet or referencebeing made to a protocol kind of in the external packet in the internalpacket to restore a selected internal packet into the external packet.26. A communication network according to claim 24 or 25, wherein twosets of the inputted source-sided logic terminal identifying informationand the destination external IP address of in the external packet areused without using the source external IP address in the externalpacket.
 27. A communication network characterized in that: acommunication network includes two or more network node units; anexternal Ether frame turning into an internal packet under the controlof a unit control table of the network node unit; the internal packetbeing transferred within the communication network; the internal packetbeing restored as an external Ether frame under the control of a unitcontrol table of the network node unit; the unit control table includingaddress information related, at least, to an external IP packet andinternal packet; when the internal packet is formed, reference beingmade to a port number in the external IP packet in the external Etherframe to turn a selected external Ether frame into the internal packetor reference being made to a port number in the external IP packet inthe internal packet to restore the external Ether frame from a selectedinternal packet.
 28. A communication network including one or morenetwork node unit characterized in that: an external Ether frame isinputted from a logic terminal on an external communication line; bydefining three sets of logic terminal identification information on aninputted source side, a source external IP address and destinationexternal IP address in the external IP packet in the external Etherframe, an internal communication line for internal packet transfer beingdefined between the source-sided and destination-sided network nodeunits under the control of unit control tables of within source-sidedand destination-sided network node units and a control table of a relayunit; when the internal packet is formed, reference being made to a portnumber in the external IP packet in the external Ether frame to turn aselected external Ether frame into an internal packet or reference beingmade to a port number in the external IP packet in the internal packetto restore the external Ether frame from a selected internal packet. 29.A communication network according to claim 27 or 28, wherein separatedinto a plurality of internal communication networks by a method totransfer the internal packet into a non-overlapped network according toa port number value in the external IP packet.
 30. A method forseparating, for a communication network according to claim 27 or 28, acommunication network into a plurality of internal communicationnetworks by a method to transfer the internal packet into anon-overlapped network according to a port number value in the externalIP packet.
 31. A communication network according to claim 27 or 28,wherein the internal packet is any of an IPv4, an IPv6, an Ether frame,an MPLS frame and an HDLC network.
 32. A terminal-to-terminalcommunication connection control method characterized in that: an IPnetwork includes two or more network node units; an external packetforwarded from a terminal unit 1 turning into an internal packet underthe control of a unit control table of the network node unit; theinternal packet being transferred within the IP network; the internalpacket being restored as an external packet under the control of a unitcontrol table of the network node unit; the unit control table includingaddress information related, at least, to the external packet andinternal packet; reference being made to a protocol kind of in theexternal packet to turn a selected external packet into the internalpacket or reference being made to a protocol kind of in the externalpacket in the internal packet to enable restoration of a selectedinternal packet into the external packet; the restored external IPpacket reaching a terminal unit
 2. 33. A terminal-to-terminalcommunication connection control method characterized in that: an IPnetwork includes two or more network node units; an external packetforwarded from a terminal unit 1 turning into an internal packet underthe control of a unit control table of the network node unit; theinternal packet being transferred within the IP network; the internalpacket being restored as an external packet under the control of a unitcontrol table of the network node unit; the unit control table includingaddress information related, at least, to the external packet andinternal packet; when the internal packet is formed, reference beingmade to a port number in the external packet to turn a selected externalpacket into the internal packet or reference to be made to a port numberin the external packet in the internal packet to enable restoration ofthe external packet from a selected internal packet; the restoredexternal IP packet reaching a terminal unit
 2. 34. Aterminal-to-terminal communication connection control methodcharacterized in that: a communication network includes two or morenetwork node units; an external Ether frame forwarded from a terminalunit 1 turning into an internal packet under the control of a unitcontrol table of the network node unit; the internal packet beingtransferred within the communication network; the internal packet beingrestored as the external Ether frame under the control of a unit controltable of the network node unit; the unit control table including addressinformation related, at least, to the external packet and internalpacket; reference being made to a protocol kind of in the external IPpacket in the external Ether frame to turn a selected external Etherframe into the internal packet or reference being made to a protocolkind of in the external IP packet in the internal packet to restore theexternal Ether frame from a selected internal packet, the restoredexternal Ether frame reaching a terminal unit
 2. 35. Aterminal-to-terminal communication connection control methodcharacterized in that: a communication network includes two or morenetwork node units; an external Ether frame forwarded from a terminalunit 1 turning into an internal packet under the control of a unitcontrol table of the network node unit; the internal packet beingtransferred within the communication network; the internal packet beingrestored as an external Ether frame under the control of a unit controltable of the network node unit; the unit control table including addressinformation related, at least, to the external packet and internalpacket; when the internal packet is formed, reference being made to aport number in the external packet to turn a selected external packetinto the internal packet or reference being made to a port number in theexternal packet in the internal packet to restore the external Etherframe from a selected internal packet; the restored external Ether framereaching a terminal unit
 2. 36. A communication function circuit used inthe network node unit, wherein the communication function circuit has afunction to select the external packet according to a protocol kind ofan external packet of a communication network according to claim
 14. 37.A communication function circuit used in the network node unit, whereinthe communication function circuit has a function to select the externalpacket according to a port number in an external packet in the networknode unit of a communication network according to claim
 18. 38. Acommunication function program module used in the network node unit,wherein the communication function program module has a function toselect the external packet according to a protocol kind of an externalpacket of the communication network according to claim 14 or
 24. 39. Acommunication function program module used in the network node unit,wherein the communication function program module has a function toselect the external packet according to a port number in an externalpacket of a communication network according to claim 18 or
 27. 40. Abilling method for charging communication fee by specifying a relevantcommunication record with using a record ID, for an IP network accordingto claim 14 or 18,
 41. A method for temporarily suspending andrecovering an encapsulation and decapsulation function using a relevantcommunication record by the use of a record effective bit in thecommunication record, for an IP network according to claim 14 or
 18. 42.A network node unit used for carrying out an IP network according toclaim 14 or
 18. 43. A communication function circuit in a network nodeunit, wherein the communication record in the control table of withinthe network node unit in the communication network according to claim 24includes an internal source IP address, an internal destination IPaddress, a source network address, a destination network address, asource IP address mask, a destination IP address mask, an internalinterface, an external interface and a record ID.
 44. A communicationfunction circuit in a network node unit, wherein a particular bit in thecommunication record is a memory protection bit for allowing orprohibiting rewriting of the relevant communication record of a controlrecord in the network node unit within the communication networkaccording to claim 24, having a function to prohibit the communicationrecord from being rewritten when the memory protection bit is “1” andallow the communication record to be rewritten when the memoryprotection bit is “0”.
 45. An IP network characterized in that: an IPnetwork includes two or more network node units; an external packetturning into an internal packet under the control of a unit controltable of the network node unit; the internal packet being transferredwithin the IP network; the internal packet being restored as theexternal packet under the control of the unit control table of thenetwork node unit; the unit control table including address informationrelated, at least, to the external packet and internal packet; adestination-sided network node unit has a multicast recipient addressconverting function being included to send an external packet restoredby conversion into individual IP addresses and port numbers ofreception-sided terminal units.
 46. An IP network including one or morenetwork node unit characterized in that: an external packet is inputtedfrom a logic terminal on an external communication line; by definingthree sets of logic terminal identification information on an inputtedsource side, a source external IP address and destination external IPaddress in the external packet, a destination internal address as adestination of transfer of the internal packet being defined under thecontrol of a unit control table of within a source-sided network nodeunit; the internal packet being transferred within an IP network; amulticast recipient address converting function being included to send,from a destination-sided network node unit, an external packet restoredby conversion into individual IP addresses and port numbers ofreception-sided terminal units.
 47. An IP network including one or morenetwork node unit characterized in that: an external packet is inputtedfrom a logic terminal on an external communication line; by definingthree sets of logic terminal identification information on a sourceside, a source external IP address and destination external IP addressin the external packet, an internal communication line for internalpacket transfer being defined between source-sided and destination-sidednetwork node units under the control of unit control tables of withinthe source-sided and destination-sided network node units and a controltable of a relay unit; a multicast recipient address converting functionbeing included to send, from a destination-sided network node unit, anexternal packet restored by conversion into individual IP addresses andport numbers of reception-sided terminal units.
 48. Aterminal-to-terminal communication connection control methodcharacterized in that: an IP network includes two or more network nodeunits; an external packet forwarded from a terminal unit 1 turning intoan internal packet under the control of a unit control table of thenetwork node unit; the internal packet being transferred within the IPnetwork; the internal packet being restored as an external packet underthe control of a unit control table of the network node unit; the unitcontrol table including address information related, at least, to theexternal packet and internal packet; a multicast recipient addressconverting function being included to send, from a destination-sidednetwork node unit, an external packet restored by conversion intoindividual IP addresses and port numbers of reception-sided terminalunits.
 49. A terminal-to-terminal communication connection controlmethod for carrying out a multicast recipient address convertingfunction characterized in that: an IP network includes two or morenetwork node units; an external packet forwarded from a terminal unit 1is inputted at a logic terminal on an external communication line; bydefining three sets of logic terminal identification information on aninputted source side, a source external IP address and destinationexternal IP address in the external packet, a destination internaladdress as a destination of transfer of the internal packet beingdefined under the control of a unit control table of within asource-sided network node unit; the internal packet being transferredwithin a communication network; a function being included to send anexternal packet restored by conversion into individual IP addresses andport numbers of reception-sided terminal units, from a destination-sidednetwork node unit to a plurality of terminal units.
 50. Aterminal-to-terminal communication connection control method forcarrying out a multicast recipient address converting functioncharacterized in that: an IP network includes two or more network nodeunits; an external packet forwarded from a terminal unit 1 is inputtedat a logic terminal on an external communication line; by defining threesets of logic terminal identification information on a source side, asource external IP address and destination external IP address in theexternal packet, an internal communication line for internal packettransfer being defined between source-sided and destination-sidednetwork node units under the control of unit control tables of withinsource-sided and destination-sided network node units and a controltable of a relay unit; a function being included to send an externalpacket restored by conversion into individual IP addresses and portnumbers of reception-sided terminal units, from a destination-sidednetwork node unit to a plurality of terminal units.
 51. A network nodeunit including a multicast function used for a terminal-to-terminalcommunication connection control method according to claim 48 .
 52. Acommunication function circuit having a function to select an externalpacket according to a protocol kind in an external packet used in thenetwork node unit according to claim
 51. 53. A communication functionprogram module for carrying out a function to select an external packetaccording to a protocol kind in an external packet used in the networknode unit according to claim
 51. 54. An IP network according to claim18, wherein an information safety degree of an IP network is increasedby carrying out at least one or more of a packet priority control, amulticast control, a signature function at the network node unit.
 55. Aterminal-to-terminal communication connection control method accordingto claim 33, wherein an information safety degree of an IP network isincreased by carrying out at least one ore more of a packet prioritycontrol, a multicast control, a signature function at the network nodeunit.
 56. A network node unit to be used in the IP network according toclaim
 54. 57. A communication function circuit to be used in the IPnetwork according to claim
 56. 58. A communication function programmodule to be used in the IP network according to claim
 56. 59. Acommunication network characterized in that: a communication networkincludes two or more network node units, a packet being inputted at alogic terminal at an end of an external communication line to thenetwork node unit, the packet selected, in a source-sided network nodeunit, by an address inspection using registration information of withinthe network node unit being transferred within the communicationnetwork, the packet in a destination-sided network node unit beingselected by an address inspection and forwarded onto an externalcommunication line 2 via a logic terminal, the network node unitcarrying out one or more of a packet filter function, packet prioritycontrol, multicast control and signature function, using at least aprotocol kind and port number thereby improving information securityover the communication network.
 60. A network node unit used in acommunication network according to claim
 59. 61. A terminal-to-terminalcommunication connection control method characterized in that: an IPnetwork includes 2 or more network node units; in a terminal-to-terminalcommunication connection control procedure passing by way of a terminalunit 1, a media router 1 or radio base point 1, a telephone managementserver 1, a telephone management server 2, a media router 2 or radiobase point 2 and a terminal unit 2, the terminal unit and the mediarouter or radio base point have a communication with a communicationprocedure based on an interface individual between the terminals; acommunication procedure of between the media router or radio base pointand the telephone management server being a UNI for the media router orUNI for the radio base point; a communication procedure of between thetelephone management server and another telephone management serverbeing standardized within the communication network, the telephonemanagement server including at least a function to carry out a UNI forthe radio base point.
 62. A terminal-to-terminal communicationconnection control method according to claim 61, wherein a communicationprocedure of between the telephone management server 1 and the telephonemanagement server 2 is an NNI based on a common channel signalingsystem.
 63. A terminal-to-terminal communication connection controlmethod according to claim 61, wherein the telephone management server 1and the telephone management server 2 are carried out as a sametelephone management server, to use a communication line connecting theterminal unit 1, the media router 1 or radio base point 1, the telephonemanagement server, the media router 2 or radio base point 2 and theterminal unit
 2. 64. A terminal-to-terminal communication connectioncontrol method according to claim 61, wherein the UNI for the mediarouter or radio base point is acquired by an inquiry of from thetelephone management server to a telephone number server, and thetelephone management server uses the acquired UNI for the communicationprocedure management.
 65. A terminal-to-terminal communicationconnection control method according to claim 64, wherein the acquiredUNI is recorded to a CIC management table under the management of thetelephone management server and used in a communication proceduremanagement.
 66. An IP network characterized in that: an IP networkincludes two or more network node units; an external packet forwardedfrom a media router 1 or radio base point 1 turning into an internalpacket in the source-sided network node unit; the internal packet beingtransferred within the communication network; the internal packet beingrestored into an external packet in the destination-sided network nodeunit and forwarded to a media router 2 or radio base point 2; acommunication procedure of between the media router or radio base pointand the telephone management server being a UNI for the media router orradio base point in order for communication connecting, from acommunication line, a terminal unit 1, a media router 1 or radio basepoint 1, a telephone management server 1, a telephone management server2, a media router 2 or radio base point 2 and a terminal unit 2; acommunication procedure of between the telephone management server andthe telephone management server being to carry out aterminal-to-terminal communication connection control method of an NNIbased on a common channel signaling system.
 67. An IP networkcharacterized in that: an IP network includes two or more network nodeunits; an external packet forwarded from a media router 1 or radio basepoint 1 being inputted at a logic terminal on an external communicationline; by defining three sets of logic terminal identificationinformation on an inputted source side, a source external IP address anddestination external IP address in the external packet, a destinationinternal address as a destination of transfer of the internal packetbeing defined under the control of a unit control table of within asource-sided network node unit; the internal packet being transferredwithin a communication network; the internal packet being restored intoan external packet in a destination-sided network node unit andforwarded to a media router 2 or radio base point 2; a communicationprocedure of between the media router or radio base point and thetelephone management server being a UNI for the media router or radiobase point in order for communication connecting, from a communicationline, a terminal unit 1, a media router 1 or radio base point 1, atelephone management server 1, a telephone management server 2, a mediarouter 2 or radio base point 2 and a terminal unit 2; a communicationprocedure of between the telephone management server and the telephonemanagement server being to carry out a terminal-to-terminalcommunication connection control method of an NNI based on a commonchannel signaling system.
 68. An IP network characterized in that: an IPnetwork includes two or more network node units; an external packetforwarded from a media router 1 or radio base point 1 being inputted ata logic terminal on an external communication line; by defining threesets of logic terminal identification information on a source side, asource external IP address and destination external IP address in theexternal packet, an internal communication line for internal packettransfer being defined between source-sided and destination-sidednetwork node units under the control of unit control tables of withinthe source-sided and destination-sided network node units and a controltable of a relay unit; the internal packet being transferred within acommunication network and restored into an external packet in thedestination-sided network node unit and forwarded to a media router 2 orradio base point 2; a communication procedure of between the mediarouter or radio base point and the telephone management server being aUNI for the media router or radio base point in order for communicationconnecting, from a communication line, a terminal unit 1, a media router1 or radio base point 1, a telephone management server 1, a telephonemanagement server 2, a media router 2 or radio base point 2 and aterminal unit 2; a communication procedure of between the telephonemanagement server and the telephone management server being to carry outa terminal-to-terminal communication connection control method of an NNIbased on a common channel signaling system.
 69. An IP network accordingto claim 68, wherein two sets of the inputted source-sided logicterminal identifying information and the destination external IP addressof in the external packet are used without using the source external IPaddress in the external packet.
 70. A method for imposing telephonecommunication fee on telephone sets at least one of which is a mobilephone by specifying a relevant communication record with using acommunication record ID within the unit control table, for an IP networkaccording to claim
 66. 71. A terminal-to-terminal communicationconnection control method according to claim 61, wherein in aterminal-to-terminal communication at least one is a mobile phone, anoutgoing call management table being used to regulate the number ofoutgoing calls.
 72. A terminal-to-terminal communication connectioncontrol method according to claim 61, wherein in a terminal-to-terminalcommunication at least one is a mobile phone, an incoming callmanagement table being used to regulate the number of incoming calls.73. An IP network according to claim 66, wherein in aterminal-to-terminal communication at least one is a mobile phone, anoutgoing call management table being used to regulate the number ofoutgoing calls.
 74. An IP network according to claim 66, wherein in aterminal-to-terminal communication at least one is a mobile phone, anincoming call management table being used to regulate the number ofincoming calls.
 75. A terminal-to-terminal communication connectioncontrol method according to claim 61, wherein in a terminal-to-terminalcommunication at least one is a mobile phone, an operation serverinquiring the telephone management server to acquire information of inthe CIC management table used in the terminal-to-terminal communicationthereby billing communication fee.
 76. An IP network according to claim66, wherein in a terminal-to-terminal communication at least one is amobile phone, an operation server inquiring the telephone managementserver to acquire information of in the CIC management table used in theterminal-to-terminal communication thereby billing communication fee.77. A radio base point to be used connected to a network node unit of anIP network according to claim 66, including an IP communication lineinterface section, a radio interface section and a radiotransmitting/receiving section, the radio transmitting/receiving sectionbeing capable of telephone-communicating with any one or more of a radiocommunication path for analog mobile phones, a radio communication pathfor digital mobile phones and a radio communication path for IP mobilephones.
 78. A radio base point characterized according to claim 77,wherein the IP communication line interface section uses a radiocommunication path—IP address correspondence table to manage an IPaddress a mobile phone uses.
 79. An IP network according to claim 66,wherein the internal packet is any one of an IPv4, an IPv6, an Etherframe, an MPLS frame and an HDLC frame.
 80. A terminal-to-terminalcommunication connection control method using an IP networkcharacterized in that: the IP network includes 2 or more network nodeunits; a terminal 1 and terminal 2 carries out a high levelcommunication start procedure at between the two terminals through an IPnetwork by using telephone numbers wherein a communication path isestablished according to a line connection control procedure applying acommon channel signaling system to the IP network, and thereaftercarries out a terminal-to-terminal media communication; upon ending theterminal-to-terminal media communication, the communication path beingreleased in the IP network by a line connection control procedureapplying a common channel signaling system to the IP network to carryout a terminal unit high level communication closing procedure therebyeffecting a multimedia communication.
 81. A terminal-to-terminalcommunication connection control method using an IP network according toclaim 80, wherein an IP packet storing a voice and image is communicatedas the terminal-to-terminal multimedia communication.
 82. Aterminal-to-terminal communication connection control methodcharacterized in that: an IP network includes a network node unit 1 anda network node unit 2, a terminal unit 1 sending to the network nodeunit 1 an IP packet requesting a communication containing anidentification name 1 of the terminal unit 1 and identification name 2of the terminal unit 2; the internal packet containing an identificationname 1 and identification 2 reaching a telephone management server 1;the telephone management server 1 acquiring and sending back an IPaddress and port number corresponding to the identification name 2through a telephone number server; the telephone management server 1notifying the telephone management server 2 of a communication requestof from the terminal unit 1 to the terminal unit 2; the telephonemanagement server 1 asking a table management server 1 to set in thenetwork node unit 1 a communication record for encapsulation of an IPpacket to be communicated between the terminal unit 1 and the terminalunit 2; the telephone management server 2 asking a table managementserver 2 to set in the network node unit 2 a communication record forencapsulation of an IP packet to be communicated between the terminalunit 1 and the terminal unit 2; the terminal unit 1 receiving an IPpacket containing the IP address and port number via the network nodeunit 1; terminal unit 1 forwarding an IP packet having an IP address andport number corresponding to the acquired identification name 2; the IPpacket in the network node unit 1 being encapsulated into an internalpacket by the use of the set communication record; the internal packetbeing transferred within a communication network to reach the networknode unit 2 and, in the network node unit 2, decapsulated by the use ofthe set communication record to reach the terminal 2; the telephonemanagement server 1 and the telephone management server 2, upon a lapseof a constant time, deleing the communication records.
 83. Aterminal-to-terminal communication connection control method accordingto claim 82, wherein the identification name 2 responds only in IPaddress but does not respond in port number, and the telephonemanagement server uses an opened value of a port number corresponding tothe identification name
 2. 84. A terminal-to-terminal communicationconnection control method according to claim 82, wherein the terminal 1or terminal 2 forwards an IP packet of communication end whereby thetelephone management server asks the table management server to delete acommunication record to be used for the terminal unit 1 and terminalunit 2 but not to delete the communication record by a lapse of constanttime.
 85. An IP network according to claim 66, wherein the telephonenumber is a telephone number to be used on a fixed telephone set ormobile phone, attendant information to the telephone number including atleast an external IP address of a telephone set having the telephonenumber or external IP address of a media router to connect the telephoneset being registered to the telephone number server via a user serviceserver and telephone management server.
 86. An IP network according toclaim 85, wherein the telephone number is a telephone number to be usedon a mobile phone, upon registration to the telephone number server aterminal authentication procedure being carried out to confirm acorrectness of the telephone number and the telephone-number attendantinformation.
 87. An IP network according to claim 85, wherein thetelephone number server holds, of the telephone-number attendantinformation, at least an external IP address of a media router the fixedtelephone set is to connect and an internal IP address of a logicterminal on a side of a network node unit the media router is to connectvia a communication line.
 88. An IP network according to claim 86,wherein the telephone number server holds an external IP address as themobile telephone set as telephone-number attendant information and aninternal IP address of a logic terminal on a side of a network node unitto be connected via a communication line by the radio base point to beconnected by the mobile telephone set.
 89. An IP network according toclaim 85 or 86, wherein the telephone number server is allowed toinquire another telephone number server thereby acquiringtelephone-number attendant information possessed by the other telephonenumber server.
 90. An IP network characterized in that: an IP networkincludes two or more network node units and two or more radio basepoints, a voice transmitted from a mobile phone 1 reaching a radio basepoint 1 via a radio communication path to be turned, in the radio basepoint 1, into an external IP packet containing a digital voice; theexternal IP packet containing a digital voice being inputted to thenetwork node unit via a communication line 1 and turned into an internalpacket, transferred in an IP network to reach a destination-sidednetwork node unit and restored as an external packet containing adigital voice, and transferred to a radio base point 2 via acommunication line 2 and being reachable to a mobile phone 2 via a radiobase point; the voice transmitted from the fixed telephone set 1reaching a media router 1 at an outside of the IP network to be turned,in the media router 1, into an external IP packet containing a digitalvoice; the external IP packet being inputted to the network node unitvia a communication line 3, transferred in the IP network to reach thedestination-sided network node unit and restored as an external IPpacket containing a digital voice, reaching a media router 2 at anoutside of the IP network via a communication line 4, and turned into avoice in the media router 2 and being reachable to a fixed telephone set2; telephone communication being possible between the mobile phone andthe fixed telephone set via the IP network; communication between mobilephones and communication between mobile phones being both possible. 91.An IP network according to claim 90, wherein an encapsulation functionin the network node unit is used to turn the external IP packet into aninternal packet, the packet being transferred within a communicationnetwork, the network node unit carrying out one or more of a packetfilter function, packet priority control, multicast control and asignature function, using at least a protocol kind or port numberthereby improving information security over the communication network.92. An IP network according to claim 91, wherein the unit control tablein the network node unit is used for turning into an internal packet, inthe source-sided network node unit the internal packet selected by anaddress inspection using registration information of within the networknode unit being transferred within the communication network, thenetwork node unit carrying out an address inspection and one or more ofa packet filter function, packet priority control, multicast control andsignature function, using at least a protocol kind or port numberthereby improving information security over the communication network.93. An IP network characterized in that: an IP network comprises aplurality of IP networks N1, N2, . . . ; an IP network N-m and an IPnetwork N-n are connected through another IP network N-k; a telephonenumber server for connection to the IP network N1 can acquire an IPaddress and related information related to a telephone number managed bya superior telephone number server 2 by way of a superior telephonenumber server 1 for connection to an IP network N1 and a superiortelephone number server 2 for connection to an IP network N2.
 94. An IPnetwork according to claim 90, wherein a user is to offer a registrationof a mobile phone by attaching at least a telephone number and mobilephone address while an accepter is to notify the user of terminal-unitauthentication information and a proxy mobile phone server address, theuser being to set the telephone number, the mobile phone address, theterminal-unit authentication information and the proxy mobile phoneserver address onto the mobile phone, the superior telephone numberserver holding at least the telephone number and terminal-unitauthentication information in the telephone number server thereby makinga telephone number registration of the mobile phone.
 95. An IP networkaccording to claim 90, wherein the mobile phone transmits positionregistration request information, an external packet containing theposition registration request information being turned into an internalpacket via the network node unit and delivered to a superior telephonenumber server, the superior telephone number server using the telephonenumber and terminal-unit authentication information of the mobile phoneincluded in the received at least position registration request and thetelephone number and terminal-unit authentication information held in atelephone number registration procedure of the telephone set of theinformation mobile phone, to carry out an authentication procedure as towhether the mobile phone is a normal telephone set thereby registeringan initial position of the mobile phone.
 96. An IP network according toclaim 90, wherein the mobile phone transmits position change requestinformation, an external packet containing the position change requestinformation being turned into an internal packet via the network nodeunit and delivered to a superior telephone number server, the superiortelephone number server using the telephone number and terminal-unitauthentication information of the mobile phone included in the receivedat least position change request and the telephone number held in atelephone number registration procedure of the telephone set of theinformation mobile phone and terminal-unit authentication information,to carry out an authentication procedure as to whether the mobile phoneis a normal telephone set and transmit information concerning the mobilephone to a telephone number server or superior telephone number servermanaging a changed position of the mobile phone thereby carrying out aposition change procedure of the mobile phone.
 97. An IP networkcharacterized in that: an IP network includes two or more network nodeunits; an external packet sent from one or more terminal units beinginputted at a logic terminal at an end of an external communication line1 to the source-sided network node unit; an internal packet being formedfrom a selected external packet; the internal packet being transferredwithin a communication network; the internal packet in thedestination-sided network node unit being restored into an externalpacket from a selected internal packet and forwarded onto an ASP sitevia an external communication line 2 in the IP network; an inverse IPpacket transmission is capable; at least when the internal packet isformed or the external IP packet is restored, at least one of a protocoland a port number within the external IP packet being to be used;thereby improving the communication security of an IP transmissionbetween the ASP site and the terminal unit.
 98. An IP network accordingto claim 97, wherein the programs in the ASP site are servers of aclient server model.
 99. An IP network according to claim 97, whereinthe programs in the ASP site allow servers of a client server model andclients to coexist.
 100. An IP network characterized in that: an IPnetwork includes two or more network node units; programs in an ASP sitesending an external packet onto one or more terminal unit; the externalpacket being inputted at a logic terminal at an end of an externalcommunication line 1 to the source-sided network node unit; an internalpacket being formed from a selected external packet; the internal packetbeing transferred within a communication network; the internal packetincluding a function to be restored from an internal packet selected inthe destination-sided network node unit into the external packet andforwarded onto an external communication line 2 in the IP network; atleast when the internal packet is formed or the external IP packet isrestored, at least one of a protocol and a port number within theexternal IP packet being to be used; an IP packet being to be sent fromthe terminal unit to the program of in the ASP site; the programs in theASP site operating as a client of a client server model while theprogram at the terminal unit operating as a server of the client servermodel thereby improving the communication security of server or programin the ASP site.
 101. A LAN leasing method characterized in that: an IPnetwork includes 2 or more network node unites; in a case that Company Aleases a LAN to use the LAN via an IP network, a communication record isset in a unit control table of in a network node unit within the IPnetwork in order to communicate an IP packet between a terminal unit ofCompany A and resources in the leased LAN while a communication recordis not set in unit control tables of in all network node units withinthe IP network in order to make impossible to communicate an IP packetbetween a terminal unit other than the terminal unit of Company A andthe resources in the leased LAN; an encapsulation function being used ina source-sided network node unit while a decapsulation function beingused in a destination-sided network node unit whereby a LAN leaserleases out the LAN.
 102. A joint utilizing method wherein an IP networkincludes 2 or more network node unites, Company X to Company Z set acommunication record in a unit control table of in a network node unitwithin the IP network in order to respectively communicate IP packetswith the ASP site while the other than Company X to Company Z do not setin all network node units a communication record enabling communicationof the ASP site and IP packet; an encapsulation function being used in asource-sided network node unit while a decapsulation function being usedin a destination-sided network node unit whereby two or more companiesutilize the ASP site in a joint fashion.
 103. A LAN leasing methodcharacterized in that: an IP network includes 2 or more network nodeunites; in a case that Company A leases a LAN to use the LAN via an IPnetwork, a communication record is set in a unit control table of in anetwork node unit within the IP network in order to communicate an IPpacket between a terminal unit of Company A and resources in the leasedLAN while a communication record is not set in unit control tables of inall network node units within the IP network in order to make impossibleto communicate an IP packet between a terminal unit other than theterminal unit of Company A and the resources in the leased LAN; in asource-sided network node unit, the packet selected by an addressinspection using registration information of within the network nodeunit being transferred within a communication network whereby a LANleaser leases out the LAN.
 104. A joint utilizing method wherein an IPnetwork includes 2 or more network node unites; Company X to Company Zset a communication record in a unit control table of in a network nodeunit within the IP network in order to respectively communicate IPpackets with an ASP site while the other than Company X to Company Zdoes not set in all network node units a communication record ofenabling communication of the ASP site and IP packet; in a source-sidednetwork node unit, the packet selected by an address inspection usingregistration information of within the network node unit beingtransferred within a communication network whereby two or more companiesutilize the ASP site in a joint fashion.
 105. A method of multicast datadistribution onto mobile terminal units characterized in that: an IPnetwork includes 2 or more network node unites; records for multicastdata distribution are previously set in network node units and routersin an IP network respectively; in the case that an external packetcontaining multicast data is sent from a fixed terminal unit, theexternal packet reached the source-sided network node unit being turnedinto an internal packet according to a designation of the multicast datadistributing record and transferred over an internal communication line;the internal packet when passing the router following the multicast datadistributing record of in the router; when the internal packet arrivesat the reception-sided network node unit, an external packet beingrestored from the internal packet in the reception-sided network nodeunit; the external packet containing the restored multicast data beingdelivered from the reception-sided network node unit onto one or moremobile terminal units by way of the radio base point and radiocommunication path.
 106. A method of multicast data distribution ontomobile terminal units according to claim 105, wherein multicast data canbe distributed also from the reception-sided network node unit via amedia router onto one or more fixed terminal units.
 107. A method ofmulticast data distribution onto mobile terminal units according toclaim 105, wherein the mobile terminal unit issues a multicast receptionrequest including at least multicast reception terminal-unitauthentication information, wherein when a multicast authenticationserver is allowed for multicast reception, a table management server isasked to rewrite the multicast distributing record of in the networknode unit thereby making the mobile terminal unit receivable.
 108. Amethod of multicast data distribution onto mobile terminal unitsaccording to claim 105, wherein a multicast authentication servernotifies a user service server of multicast reception permission therebymaking possible use also as billing information.
 109. A method ofmulticast data distribution onto mobile terminal units according toclaim 105, wherein the mobile terminal unit issues a multicast receptionrequest, the multicast authentication server not carrying out aprocedure of authentication for the multicast reception terminal unitbut asking the table management server to rewrite the multicastdistributing record of in the network node unit thereby enablingcharge-free reception on the mobile terminal unit.
 110. A method ofmulticast data distribution onto mobile terminal units according toclaim 105, wherein multicast data is transmitted from a fixed terminalunit, multicast data being transmitted from a mobile terminal unit inplace of transfer via the media router and transferred within the IPnetwork via the radio base point.
 111. An IP network allowed formulticast distribution onto mobile terminal units according to claim105, wherein the IP network includes two or more network node units, anexternal packet sent from terminal units of one or more utilizers beinginputted at a logic terminal at an end of an external communication line1 to the source-sided network node unit, an internal packet being formedfrom a selected external packet, the internal packet being transferredwithin a communication network, the internal packet in thedestination-sided network node unit being restored from a selectedinternal packet into the external packet and forwarded onto an externalcommunication line
 2. 112. A terminal-to-terminal communicationconnection control method using an IP network according to claim 1 or 2,wherein an external IP packet being inputted at a logic terminal at anend of a communication line, the external IP packet being turned into aninternal packet under the control of the address management table of inthe source-sided network node unit, the internal packet beingtransferred within the IP network to reach the destination-sided networknode unit, the internal packet being restored as an external IP packetunder the control of the address management table of in thedestination-sided network node unit and forwarded onto an externalcommunication line.
 113. A TV conference communication method using anIP network, wherein an IP network includes two or more network nodeunits, an external IP packet being inputted at a logic terminal at anend of a communication line, the external IP packet being turned into aninternal packet under the control of the address management table formulticast of in the source-sided network node unit, the internal packetbeing transferred within the IP network to reach the destination-sidednetwork node unit, a path table set for multicast is used in the routerof the IP network, the internal packet being restored as an external IPpacket under the control of the address management table of in thedestination-sided network node unit and forwarded onto an externalcommunication line.
 114. A relay gateway used for carrying out aterminal-to-terminal communication connection control method using an IPnetwork according to claim 1, 2, 61 or 80, including a communicationline having an interface of a ST based on a common channel signalingsystem or NNI based on a mobile communication network, a communicationline having an IP-network-sided NNI interface based on the commonchannel signaling system, relay control section and a voice controlsection.
 115. A relay gateway according to claim 114, wherein the voicecontrol section is to be mounted separately on a plurality of boards.116. A TV conference communication method using an IP network accordingto claim 113, wherein a transmission right is changed bytransmitting/receiving an IP packet including a transmission rightchange information at terminal units,
 117. A TV conference communicationmethod using an IP network according to claim 113, wherein a unitcontrol table is used for the address management table.
 118. A TVconference communication method using an IP network according to claim113, wherein a unit control table is used for the address managementtable, an address inspection is carried out by using the unit controltable and an IP encapusulation is not carried out.
 119. Aterminal-to-terminal communication connection control method accordingto claim 83, wherein a port control filter including a port filter 1 isset at the another communication record in the network node unit 2 for acommunication between the terminal units 1 and 2, and a destination portnumber of the IP packet of which the terminal unit 2 receives islimited.
 120. A terminal-to-terminal communication connection controlmethod characterized in that: an IP network includes two or more networknode units; a terminal unit 1 requests a communication for the terminalunit 2 to the IP network by using the identification name of theterminal unit 2; the IP network sets a unit control table for thecommunication between the terminal units 1 and 2 in network node units 1and 2; an external packet is sent from the terminal unit 1; the externalIP packet is converted into an internal IP packet at the network nodeunit 1; the internal IP packet is transferred within the IP network; theinternal IP packet restores only an external IP packet including a portnumber of the terminal unit 2 set at the unit control table in thenetwork node unit and sends it to the terminal unit 2; when the externalIP packet is transferred reversely above, the external IP packet isconverted into the internal IP packet at the network node unit 2; andthe internal IP packet is transferred within the IP network; theinternal IP packet is restored to the external IP packet.
 121. Aterminal-to-terminal communication connection control method using an IPnetwork according to claim 120, wherein when the external IP packet istransferred reversely and converted into the internal IP packet, onlythe external IP packet including the port number of the terminal unit 2set at the unit control table in the network node unit 2 is convertedinto the internal IP packet.
 122. A terminal-to-terminal communicationconnection control method using an IP network according to claim 120,wherein only the external IP packet including the port number of theterminal unit 2 set at the unit control table in the network node unit 2is converted into the internal IP packet; and at the reversecommunication, the internal IP packet received by the network node unit1 is restored to the external IP packet including the port number of theterminal unit 2 set at the unit control table in the network node unit1.
 123. A terminal-to-terminal communication connection control methodusing an IP network according to claim 120, wherein the terminal unit 1obtains the IP address of the terminal unit 2 by showing theidentification name of the terminal unit 2 to the telephone numberserver in the IP network.
 124. A terminal-to-terminal communicationconnection control method using an IP network according to claim 120,wherein at least a port number designating e-mail function or a portnumber designating WWW function is includes as the port number of theterminal unit 2, and the terminal unit 2 is operative for the e-mailcommunication or WWW server operation.
 125. A terminal-to-terminalsocket communication service, wherein an IP network includes 2 or morenetwork node units; an external IP packet inputted from a network nodeunit 1 is converted into an internal packet under a unit control tablein the network node unit 1; the internal IP packet is transferred withinthe IP network; the internal IP packet is restored to the external IPpacket under the unit control table in the network node unit 2; and thereverse transmission of the external IP packet is possible; the serviceincludes at least one of a function 1 and a function 2; the function 1is a function to form the internal IP packet by selecting the externalpacket based on a destination socket number in the external packetinputted to the unit control table of a transmitting side; the function2 is a function to select the external IP packet for restoring based ona destination socket number in the external packet restored to the unitcontrol table of a receiving side; and the IP network includes afunction to respond the IP address of the terminal unit for the questionof identification name of the terminal unit; in the IP network, pluralterminal units are connected to the network node units via communicationlines; and a communication is started by that the terminal unit 1outputs a communication request to the IP network by using theidentification name of the terminal unit
 2. 126. A terminal-to-terminalsocket communication service according to claim 125, wherein by usingthe encapsulation and decapsulation functions under the control of theunit control table in the network node unit, the network node unitcarries out at least one or more of a packet filtering function usedprotocol type, a packet priority function and a multicast function,thereby improving the security of the communication.
 127. Aterminal-to-terminal socket communication service according to claim125, wherein the network node unit carries out an address inspection,and the network node unit carries out at least one or more of a packetfiltering function used protocol type, a packet priority function and amulticast function, thereby improving the security of the communication.128. A mobile telephone set, wherein a terminal-to-terminalcommunication is capable by connecting to the IP network in the methodaccording to claim
 61. 129. A mobile telephone set, wherein a telephonecommunication is capable by connecting to the IP network in the methodaccording to claim 90.